-
Notifications
You must be signed in to change notification settings - Fork 85
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
Debian Buster arm32: "Manifest not found" using curl / TLS #562
Comments
[pdcastro] This issue has attached support thread https://jel.ly.fish/#/support-thread~af4e153f-79f1-4b28-8179-960a9f528d68 |
This is discussed at https://www.flowdock.com/app/rulemotion/i-baseimages/threads/ItT-a3BTywFhOXsGMrUrlJDTvXu and relevant upstream issue is debuerreotype/docker-debian-artifacts#68 |
[imrehg] This issue has attached support thread https://jel.ly.fish/#/support-thread~b0b90313-33c6-4f42-a623-6bd8c93c1094 |
We've changed to wget here even though it requires another package in order to circumvent this issue balena-io-library/base-images#562 Change-type: patch Signed-off-by: Chris Crocker-White <chriscw@balena.io>
[chrisys] This issue has attached support thread https://jel.ly.fish/#/support-thread~06cc4d80-5f5c-43a3-8858-415cc89a793c |
It works with
|
[pdcastro] This issue has attached support thread https://jel.ly.fish/#/support-thread~ca6f7d4f-9043-4494-9a55-87b1910f15ac |
Also having issues with this, was trying to test out the latest nightlies for
|
A customer has reported that the wifi-connect project is affected by this issue, and that it was "fixed" by pinning the base image in the Dockerfile.template to "stretch":
|
Was this issue actually resolved in the base images, or is the pinning workaround still required? This issue is still referenced in https://github.com/balena-io-examples/balena-rust-hello-world/blob/master/Dockerfile.template#L19. |
hey @brownjohnf, this was fixed a while ago. Maybe the Dockerfile in the rust example is not updated (last change was on Oct 3, 2019) |
I seem to still have this problem with arm/v7, looks to me like maybe it's not fixed. |
@rfay, do you have an example of how to reproduce the issue? I have just tested with the following two Dockerfiles, using pinned / versioned base images. The old base image of May 2019 reproduces the issue, while a recent base image of August 2020 does not have the issue. Note that the
With a recent version of Docker or a very recent / latest version of the balena CLI, you could also use the |
Sorry, My problem was with the debian:buster-slim image and arm/v7, you just helped me find my way to solving it. I appreciate that very much. Sorry to stir things up. I didn't totally understand the context here, but the answer ( |
This might be a better workaround than setting environment variable, see balena-io-library/base-images#562
This might be a better workaround than setting environment variable, see balena-io-library/base-images#562
Image build fails at build.tpl#L56-L57 when
curl
can't verify host certificate:It only occurs on Debian Buster arm32 images when downloading with curl (other archs are fine) so looks like we can't use curl here until it's fixed upstream by the package maintainers. We can change to wget for now.
Note: credit to @nghiant2710 for the investigation! 👍
The text was updated successfully, but these errors were encountered: