- Notifications
You must be signed in to change notification settings - Fork928
chore: k8s example persistence & coder images#3619
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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.
Thanks for knocking this out. I didn't test it, but I assume you did. Feel free to merge if that's the case.
And, I do think it's odd how there are multiple containers. That seems like a niche use case. |
i agree - i originally considered reducing it to one container. i'll push commit reflecting this, and also include |
bpmct commentedAug 22, 2022 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
This template is called
nvm |
Uh oh!
There was an error while loading.Please reload this page.
this PR looks to address@ammario's feedback in#3588 by adding persistence to our k8s example template.
it also removes the VS Code dev container images in favor ofCoder's enterprise images. The dev container images used
/home/vscode
, which contained shell scripts/customizations that would be wiped with a/home/vscode
volume mount.open to thoughts/feedback on removing the dev container images.