Skip to content

Unable to run a 'custom' run command in the devcontainer.json #8752

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
gbraad opened this issue May 14, 2025 · 0 comments
Open
3 tasks done

Unable to run a 'custom' run command in the devcontainer.json #8752

gbraad opened this issue May 14, 2025 · 0 comments

Comments

@gbraad
Copy link

gbraad commented May 14, 2025

🐛 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:

Link to sandbox: link (optional)

Your Environment

Software Name/Version
Сodesandbox latest?
Browser Vivaldi
Operating System Fedora,/Windows,...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant