-
Notifications
You must be signed in to change notification settings - Fork 260
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
postCreateCommand deletes git config #476
Comments
@gauravsaini04 / @prathameshzarkar9 Can either of you help investigate the issue? thanks! |
Hi @luftuq, |
Hi @luftuq Thank you for raising this issue and for your patience As there hasn't been any recent activity on this issue, we're going to close it for now If you have any further updates or if the issue still persists, please feel free to reopen it or create a new issue |
Hi @gauravsaini04,
Dockerfile:
The issue is, that if I switch postCreateCommand for postStartCommand, I will get different results after rebuild. |
Hello @luftuq , Thank you for your patience and for providing simpler steps to reproduce the issue. I have one final request in this regard. You have mentioned in the issue description that certain global configurations which had moved automatically to the docker container were retained while using the postStartCommand tag. With Regards, |
Hi all,
I see inconsistent result when I run
"postCreateCommand": "git config --global user.signingkey /home/mambauser/.ssh/id_ed25519.pub"
to redirect my keys to docker folder. All other global configurations (which are moved to docker automatically) are not in container. This does not happen if I change it to
postStartCommand
. I would expect that result would be the same. Simplified devcontainer.json where it happens is here:and the dockerfile:
The text was updated successfully, but these errors were encountered: