mandatoryprogrammer / mandatoryprogrammer/CursedChrome
Issue while running docker-compose up cursedchrome
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
=> ERROR [cursedchrome 8/21] RUN /work/anyproxy/bin/anyproxy-ca --generate 0.3s
------
> [cursedchrome 8/21] RUN /work/anyproxy/bin/anyproxy-ca --generate:
0.256 /usr/bin/env: 'node\r': No such file or directory
------
failed to solve: process "/bin/sh -c /work/anyproxy/bin/anyproxy-ca --generate" did not complete successfully: exit code: 127
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with `docker-compose up cursedchrome` and inspect the `/work/anyproxy/bin/anyproxy-ca` entry point used during build step 8/21. Check why `/usr/bin/env` receives `node\r`; done means the `cursedchrome` image builds successfully past the `anyproxy-ca --generate` command.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, javascript, node.js
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100