-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
[Bug]: Custom CA certificate breaks on second container restart #734
Comments
Did your version of Docker change or were any other changes made when you upgraded the base image to 17.0.14? |
My wording was bad. It does still work if I use the old tag |
Hmm, this will be hard to track down. There have been changes since 17.0.11 that impact the truststore. In the mean time some suggested investigations / workarounds (inspired from GPT4o): Possible Causes & Fixes
|
I might have tracked down the problem. The problem is that the user provided certificates are always imported into the truststore. I found these possible solutions to the problem:
|
Please add the exact image (with tag) that you are using
eclipse-temurin:17.0.14_7-jre
Please add the version of Docker you are running
Docker version 27.4.0, build bde2b89
What happened?
When adding a custom CA certificate to the truststore, the container does not start after the second restart anymore.
This requires the re-creation of the container, e.g.,
docker compose down && docker compose up -d
.This can be reproduced with a certificate in the directory
trusted-certs
and the following Docker compose file:This used to work with older images, e.g.,
eclipse-temurin:17.0.11_9-jre
.Relevant log output
The text was updated successfully, but these errors were encountered: