-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
The container created by Devcontainer keeps resetting /etc/hosts #11439
Labels
Comments
binkoni
added a commit
to binkoni/argo-workflows
that referenced
this issue
Jul 25, 2023
Signed-off-by: Byeonggon Lee <binkoni@gonnux.com>
binkoni
added a commit
to binkoni/argo-workflows
that referenced
this issue
Jul 25, 2023
Signed-off-by: Byeonggon Lee <binkoni@gonnux.com>
binkoni
added a commit
to binkoni/argo-workflows
that referenced
this issue
Jul 26, 2023
Signed-off-by: Byeonggon Lee <binkoni@gonnux.com>
terrytangyuan
pushed a commit
that referenced
this issue
Jul 27, 2023
45 tasks
5 tasks
isubasinghe
pushed a commit
to isubasinghe/argo-workflows
that referenced
this issue
Mar 12, 2024
Signed-off-by: Byeonggon Lee <binkoni@gonnux.com>
isubasinghe
pushed a commit
to isubasinghe/argo-workflows
that referenced
this issue
May 6, 2024
Signed-off-by: Byeonggon Lee <binkoni@gonnux.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
What happened
Whenever I reboot my computer, /etc/hosts entries added by Devcontainer are gone
What I expect
/etc/hosts should be preserved
Why it happens
That's Because Devcontainer's container is running with bridge networking
https://stackoverflow.com/questions/27521678/etc-hosts-file-of-a-docker-container-gets-overwritten
How to fix It
https://code.visualstudio.com/remote/advancedcontainers/start-processesAdd postStartCommand field that adds /etc/hosts entries to devcontainer.jsonAdd --add-host options as runArgs in devcontainer.json
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
none
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: