Skip to content

Include Debian Slim image #305

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
jaztec opened this issue Oct 4, 2019 · 5 comments
Closed

Include Debian Slim image #305

jaztec opened this issue Oct 4, 2019 · 5 comments
Labels
Request Request for image modification or feature

Comments

@jaztec
Copy link

jaztec commented Oct 4, 2019

I like the small size of the Alpine image but within some project I really miss full blown features (like /dev/log for instance).

In my opinion a Debian Slim image could really by a useful midway between Alpine and full Debian, it would not diminish the right of existence for an Alpine image (can think of loads of uses there) however it would add uses for programs that are just a bit to intensive for the bare-bones Alpine installments but also don't justify a complete Debian installment either (scaling). I've looked up the base templates for the Debian setup and reiterated the request there as well: docker-library/buildpack-deps#99

Please consider adding a Debian like Slim package to the available Golang images. And of course, I do not mind contributing

@wglambert wglambert added the Request Request for image modification or feature label Oct 4, 2019
@tianon
Copy link
Member

tianon commented Nov 28, 2019

I'm not sure I understand what /dev/log has to do with Alpine, or any Docker image for that matter? /dev/log is typically a unix socket created by some user-mode application (like syslog-ng, systemd-journald, etc), not a feature of the distribution. 😕

I think the general consensus for usage of this repo is that it typically wouldn't be your runtime base and you'd use it more for building your project and then copying the resulting binary into a separate image that's FROM debian:xxx-slim, for example. (Using Docker's multi-stage builds make this especially easy to accomplish.)

@hazcod
Copy link

hazcod commented Mar 16, 2020

How about replacing the debian image with the slim variant?

@jaztec
Copy link
Author

jaztec commented Mar 16, 2020

Excuse me, it was a misunderstanding from my side. I'll close the issue

@anarcat
Copy link
Contributor

anarcat commented Oct 29, 2022

I think the general consensus for usage of this repo is that it typically wouldn't be your runtime base and you'd use it more for building your project and then copying the resulting binary into a separate image that's FROM debian:xxx-slim, for example. (Using Docker's multi-stage builds make this especially easy to accomplish.)

I still feel it would be worth using debian's slim images for this. What exactly do we need from the main debian image here that couldn't be accomplished with the slim images?

@tianon
Copy link
Member

tianon commented Oct 31, 2022

There's nothing that couldn't be accomplished with the slim images, but rather that we'd then have to duplicate the list of installed SCMs from buildpack-deps:bullseye-scm (which is what we're currently FROM).

(See also #427 where this is being actively discussed again.)

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

No branches or pull requests

5 participants