-
Notifications
You must be signed in to change notification settings - Fork 273
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
ca-certificates issue on the 1.4.0 version's docker image #2145
Comments
According to my tests it's because the ssl certificates are missing in the run image debian:bullseye-slim introduced by #2085 while they were present in gcr.io/distroless/cc-debian11 |
This is confusing me. I've used our docker image a number of times with no issues. The required certificates are present be cause we install
which wouldn't work if the required certificates were not present. You mention building your own docker image. Could that be the source of the problem? |
Ok. I know what the problem is now. You are using |
fixes: #2135 fixes: #2145 This PR repurposes the -debug image to make it the basis for a memory tracking image which we can use for investigating router memory issues via heaptrack. (https://github.com/KDE/heaptrack) The PR is a *breaking* change because it now automatically starts the router under the control of heaptrack. Technically, it's not really a breaking change and it's certainly not an API change, but I really want to draw people's attention to the fact that the debug image will now execute a lot slower than the non-debug image and use a lot more memory (to track memory with...). I've updated the docker documentation to show how to mount a local directory to store the heaptrack data. I haven't updated the kubernetes docs, because we don't go into that level of detail and we assume that a kubernetes devops person would know how to allocate and mount a PVC.
fixes: #2135 fixes: #2145 This PR repurposes the -debug image to make it the basis for a memory tracking image which we can use for investigating router memory issues via heaptrack. (https://github.com/KDE/heaptrack) The PR is a *breaking* change because it now automatically starts the router under the control of heaptrack. Technically, it's not really a breaking change and it's certainly not an API change, but I really want to draw people's attention to the fact that the debug image will now execute a lot slower than the non-debug image and use a lot more memory (to track memory with...). I've updated the docker documentation to show how to mount a local directory to store the heaptrack data. I haven't updated the kubernetes docs, because we don't go into that level of detail and we assume that a kubernetes devops person would know how to allocate and mount a PVC.
Describe the bug
Hello !
Since the latest version of the docker image (1.4.0), the router does not launch and quits panicking in hyper-rustls because of the lack of CA certificates.
I have added the trace of the error.
To Reproduce
Expected behavior
The router launches correctly.
Output
Default output :
The output with RUST_BACKTRACE=full :
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: