-
Notifications
You must be signed in to change notification settings - Fork 137
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
Cannot build v3 images: expired certificate on deb.nodesource.com #270
Comments
This is a major issue for V3 images but we are no longer maintaining this version. So the best way is upgrade to v4 or make a PR on v3 branch. |
I totally get that. Internally I also advocate for solving this by upgrading to the v4 images, so it's not a pressing issue for us. Due to this I won't dig further into fixing this for v3. I mostly wanted to report it as a heads-up in case others stumble upon this. If someone wants to tackle this, he can use this ticket as reference. |
Now I get the same error with v4: FROM thecodingmachine/php:7.4-v4-fpm-node12
USER root
RUN apt-get update
USER docker
Result:
(Also fails with Node 14/16/18) |
See my solution/workaround for now: yarnpkg/yarn#7866 (comment) |
Your issue may already be reported!
Please search on the issue tracker before creating one.
Expected Behavior
I should be able to build a container using the PHP v3 images here as base.
Current Behavior
Trying to build an image using the PHP v3 images fails due to nodesource/distributions#1266
Possible Solution
Not 100% clear yet, maybe the
ca-certificates
package must be updated before runningapt-get update
.Steps to Reproduce (for bugs)
Dockerfile
:docker build --no-cache .
in the directory of theDockerfile
This evidently works fine with the v4 images, very likely since the base system is newer and thus has more up-to-date packages:
Context
We always build custom app images using the PHP images as base which has started to fail for many of us due to the expiry of the mentioned Let's Encrypt root certificate.
Your Environment
The text was updated successfully, but these errors were encountered: