Skip to content

fix: remove built-in image for Docker template #15504

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

Merged
merged 1 commit into from
Nov 14, 2024
Merged

fix: remove built-in image for Docker template #15504

merged 1 commit into from
Nov 14, 2024

Conversation

bpmct
Copy link
Member

@bpmct bpmct commented Nov 13, 2024

The hardcoded image is an anti-pattern, leading to weird errors if the docker group is absent. We should either provide a better error in-product or just have a better image.

@matifali - also down to use a Devcontainers universal image instead or make this a parameter. Let me know what you think the best "default install" is

Copy link
Member

@matifali matifali left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We opted for the Dockerfile over the image to demonstrate that it's possible with Coder to build images on the fly without needing a registry.

But I agree that using a built image is a better practice.

@matifali
Copy link
Member

I am ok to switch to a more universal kitchen sink image, only concern is that it will make the first boot slower for new users due to image size.

@bpmct
Copy link
Member Author

bpmct commented Nov 14, 2024

Gotcha. i am going to merge this for now, and when we make a better image in coder/images we can switch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants