Using alpine running stage for docker #54

Closed
opened 2025-12-29 14:23:29 +01:00 by adam · 5 comments
Owner

Originally created by @subliker on GitHub (Apr 3, 2025).

Using scratch makes the application difficult to debug from the outside, problems with deps and others.

Originally created by @subliker on GitHub (Apr 3, 2025). Using scratch makes the application difficult to debug from the outside, problems with deps and others.
adam added the wontfix label 2025-12-29 14:23:29 +01:00
adam closed this issue 2025-12-29 14:23:29 +01:00
Author
Owner

@yusing commented on GitHub (Apr 4, 2025):

Could you elaborate more about debugging it from the outside? I don't see any benefit.

problems with deps and more

There will be no problem with deps as the container only contains the full binary and requires no dependencies.

@yusing commented on GitHub (Apr 4, 2025): Could you elaborate more about debugging it from the outside? I don't see any benefit. > problems with deps and more There will be no problem with deps as the container only contains the full binary and requires no dependencies.
Author
Owner

@subliker commented on GitHub (Apr 4, 2025):

By debug, I meant access to sh inside the container, which is simply not present in the scratch image.
If sh is not used specifically for security reasons, then you can use the distroless image to avoid copying zoneinfo and ssl certs commands separately.

@subliker commented on GitHub (Apr 4, 2025): By debug, I meant access to sh inside the container, which is simply not present in the scratch image. If sh is not used specifically for security reasons, then you can use the distroless image to avoid copying zoneinfo and ssl certs commands separately.
Author
Owner

@yusing commented on GitHub (Apr 4, 2025):

I meant access to sh inside the container

In what case should one sh into GoDoxy's container?

you can use the distroless image to avoid copying zoneinfo and ssl certs commands separately

I've just tested with distroless image, final image grown from 24MB to 30MB for no obvious benefits. I don't see the point of doing so.

Although I'm not switching to distroless from scratch for now, I'm leaving this issue opened for discussions.

@yusing commented on GitHub (Apr 4, 2025): > I meant access to sh inside the container In what case should one `sh` into GoDoxy's container? > you can use the distroless image to avoid copying zoneinfo and ssl certs commands separately I've just tested with distroless image, final image grown from 24MB to 30MB for no obvious benefits. I don't see the point of doing so. Although I'm not switching to distroless from scratch for now, I'm leaving this issue opened for discussions.
Author
Owner

@subliker commented on GitHub (Apr 5, 2025):

indeed, sh may not be needed in this case. Thanks for your attention

@subliker commented on GitHub (Apr 5, 2025): indeed, sh may not be needed in this case. Thanks for your attention
Author
Owner

@yusing commented on GitHub (Apr 5, 2025):

No problem. Please let me know if there's any other improvements can be made. Thanks for your advice.

@yusing commented on GitHub (Apr 5, 2025): No problem. Please let me know if there's any other improvements can be made. Thanks for your advice.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/godoxy-yusing#54