Running the container results in "cannot execute binary file"
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 34
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
I've followed the instructions to first run the container standalone. However in doing so I get an error, and replacing /bin/bash for /bin/sh doesn't help.
$ podman run -it nodejs/devcontainer:nightly /bin/bash
/bin/bash: /bin/bash: cannot execute binary file
I also tried building the container locally and using that to make sure I wasn't accidentally running the arm64 version on an x86_64 machine but got the same thing.
Contributor guide
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
Reproduce the reported podman run -it nodejs/devcontainer:nightly /bin/bash command, then compare it with /bin/sh and a locally built image. Check the image architecture and shell entry point against the host, using the reported arm64 and x86_64 possibilities as starting points. Done means the documented standalone container command starts a shell without the execution error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, dockerfile
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100