fix: add CA certificates to Docker image#1779
Merged
Merged
Conversation
Contributor
Author
|
I tested multiple official image versions. They all use the
The failing version panics during reqwest client initialization: I do not know which dependency change exposed the issue, but adding the standard CA bundle to the Docker image fixes the image-level problem and makes HTTPS/TLS backends work consistently. |
aawsome
approved these changes
Jun 8, 2026
aawsome
left a comment
Member
There was a problem hiding this comment.
LGTM! Thanks a lot @alexma233
Member
|
In 0.11.3 the |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Fixes #1777
This PR adds the Alpine CA certificate bundle to the final Docker image.
The runtime image still uses
scratch; it now also includes:Why
The official Docker image is currently based on
scratch. When using HTTPS/S3/REST-style backends,reqwestneeds system CA certificates for TLS verification.Without a CA bundle, rustic can panic during HTTP client initialization:
This happened with
ghcr.io/rustic-rs/rustic:latest/ rustic0.11.3while backing up to an OpenDAL B2 repository.Testing
I built and pushed a test image with this change, then used it in my Docker Compose backup setup with an OpenDAL B2 repository.
The backup completed successfully:
This confirms that TLS initialization works when the CA bundle is available in the Docker image.