codesandbox / codesandbox/codesandbox-client
Unable to run a 'custom' run command in the devcontainer.json
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
My existing devcontainer.json relies on the entrypoint defined in the dockerfile, but this causes the startup to fail.
How has this issue affected you? What are you trying to accomplish?
This means something like systemd or other init system can not be used. To enable this:
"overrideCommand": false,
"privileged": true,
is set in the devcontainer.json. This works on a local machine, and on GitHub codespaces.
To Reproduce
For example:
- https://github.com/gbraad-dotfiles/upstream/blob/main/.devcontainer/default/devcontainer.json
- https://github.com/gbraad-dotfiles/upstream/blob/main/.devcontainer/fedora/devcontainer.json
Link to sandbox: link (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | latest? |
| Browser | Vivaldi |
| Operating System | Fedora,/Windows,... |
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
Start with the two linked devcontainer.json examples and trace how Codesandbox handles devcontainer.json settings, especially overrideCommand, privileged, and the Dockerfile entrypoint. Compare this behavior with the stated local and GitHub Codespaces behavior. Done means a devcontainer using an existing entrypoint can start with the requested init system configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100