Skip to content
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

Build a debugging version of Perl #60

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

waterkip
Copy link
Contributor

Create a debugging version of Perl with gdb installed so one can take an
exact copy of the image with all the symbol tables etc etc.

generate.pl Show resolved Hide resolved
@zakame
Copy link
Member

zakame commented Mar 29, 2019

Thanks @waterkip! A debug build certainly has its uses, though just not sure if we'd want a new variant for this published on the Docker Hub, as IIRC other language images don't publish debug variants either; @tianon what do you think?

If ever, we'd also want to update the README here and https://github.com/docker-library/docs/tree/master/perl.

Create a debugging version of Perl with gdb installed so one can take an
exact copy of the image with all the symbol tables etc etc.
@tianon
Copy link
Contributor

tianon commented Mar 29, 2019

Conceptually I think this is OK, but I have a couple practical concerns with this. The first is that there are already quite a few tags on https://hub.docker.com/_/perl, and this will effectively double the number. For a real-world example of how awful this can get, see https://hub.docker.com/_/php or https://hub.docker.com/_/openjdk.

My second concern is the build time/load since we're build all these releases from source and this will effectively double that (which isn't nearly as big of a concern as the optics/usability for users, but still something to consider).

@zakame
Copy link
Member

zakame commented Mar 30, 2019

@tianon perhaps we could retain debug Dockerfiles here only in this repo and just point to it from the docs as something people can "opt in" and build locally?

It could also be a step towards providing dev/RC releases as well; they could go with debug by default.

@waterkip
Copy link
Contributor Author

@zakame I was thinking a bit along the same line.

If docker hub allows subname spaces, you could also opt for another option. Gitlab's registry allows namespaces as such: project:tag, project/subnamespace:tag, project/subnamespace/subsubnamespace:tag

We could then implement all the debug builds into their own namespace, perl/debug. Less clutter from a user perspective. Or maybe call it perl/devel if you also want development releases.

@tianon
Copy link
Contributor

tianon commented Apr 2, 2019

Both of those options sound really reasonable to me -- do y'all already have control of the perl namespace on Docker Hub? (that seems like a great place for these if so; if not, the best I can offer is contacting Docker's Support and asking real nice 😅)

@zakame
Copy link
Member

zakame commented Apr 4, 2019

@tianon tried creating perl org but it is a reserved name in Docker Hub 😅

@tianon
Copy link
Contributor

tianon commented Apr 4, 2019 via email

@mohawk2
Copy link

mohawk2 commented Sep 14, 2020

@tianon Sounds like the time for you to ask them real nice? ;-)

(it seems this PR now clashes, that would need resolving)

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.

4 participants