-
Notifications
You must be signed in to change notification settings - Fork 38
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
PyVRP devcontainer #580
base: main
Are you sure you want to change the base?
PyVRP devcontainer #580
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
I haven't tried the whole codespaces thing before but I can imagine it's pretty nice for new users that do not want to go through the hassle of setting up a local installation of everything. |
I don't understand why my custom config doesn't work
.devcontainer/setup.sh
Outdated
|
||
# Don't ask for superuser acces when debugging extensions | ||
# See https://github.com/benibenj/vscode-pythonCpp/issues/18 | ||
# echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope # errors |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This no longer works - is this due to the new jammy image?
tee: /proc/sys/kernel/yama/ptrace_scope: Read-only file system
0
The solution on SE is to run docker with --privileged but I don't know (yet) how to set this.
This PR adds a
devcontainer
folder that can be used to conveniently setup a functional development environment with Github Codespaces (and other containers). Part of #384.Notes
tasks.json
andlaunch.json
in devcontainer