Skip to content

explore dogfooding envbuilder with just the image, not a build #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

Closed
johnstcn opened this issue Aug 9, 2024 · 1 comment
Closed

explore dogfooding envbuilder with just the image, not a build #38

johnstcn opened this issue Aug 9, 2024 · 1 comment
Assignees
Labels
project/envbuilder spike Short investigation task

Comments

@johnstcn
Copy link
Member

johnstcn commented Aug 9, 2024

Until envbuilder#230 is resolved, we will not be able to perform the multi-stage build of our dogfood Dockerfile. However, we can still use the pre-built image and the devcontainer from the root of coder/coder.

Add an option to our dogfood Dockerfile to develop using envbuilder in a devcontainer!

@johnstcn
Copy link
Member Author

johnstcn commented Aug 16, 2024

See coder/coder#14324 -- Keeping this as a separate template; there are a number of workaround in place for various Kaniko things. This isn't something you can switch back and forth between in any case.

johnstcn added a commit to coder/coder that referenced this issue Aug 20, 2024
…provider (#14324)

Updates the envbuilder-dogfood template to use the envbuilder provider.
Relates to coder/internal#38

Co-authored-by: Mathias Fredriksson <mafredri@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
project/envbuilder spike Short investigation task
Projects
None yet
Development

No branches or pull requests

1 participant