-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Building of this image no longer works #184
Comments
The place to report issues with the |
I'm not sure this is an issue with the base image but I'll open an issue there too. But it is an issue for this repo as well, as a workaround can be put in place while it is fixed upstream. Any pointers on how to build docs while this gets fixed? Is there a prebuilt image pushed in the registry? |
Aha! I didn't realize this image even had a |
The issue appears to be one with |
This Dockerfile works fine. It looks like the reinstallation of FROM perl:5.20
RUN cpanm Mojolicious@5.80 |
Or maybe the mirror. Checking both |
Looks like it's just BackPAN, not CPAN: http://www.cpan.org/authors/id/S/SR/SRI/CHECKSUMS |
@kraih Heads up that the |
Ugh BackPAN, you're killing me. First we can't have SSL, now we can't have |
I guess it makes some sense since the I suppose BackPAN could maintain and sign its own |
So it looks like we don't have an even reasonably-secure way to install older deps from CPAN. 😞 Guess we'll have to just remove the "more secure" |
That's unfortunate :/ |
Thanks for the super quick response though! |
@petrosagg I'm really curious what your use-case for building this image is -- we only use it ourselves for running |
We maintain a library of arm images here https://github.com/resin-io-library which get pushed here https://registry.hub.docker.com/repos/resin/. We try to follow the official images as much as possible so that the users have the least surprises and that includes having docs on them. At the time of writing we have only ported |
Ah, makes sense.
|
Doing a clean
docker build
of this repo procuces the following error when installingMojolicious@5.80
The text was updated successfully, but these errors were encountered: