-
Notifications
You must be signed in to change notification settings - Fork 101
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
Pin all dependency versions, provide alpine-3.13
#152
Comments
I have no issue just pinning the alpine version to 3.13, especially given that the distroless version uses a pinned 3.12 alpine as a pre-build step to download the deno binary. |
wperron
added a commit
to wperron/deno-docker
that referenced
this issue
Aug 11, 2021
Make does not work with alpine 3.14, this commit pins the alpine version to 3.13 to fix the issue. Fixes denoland#152
wperron
added a commit
to wperron/deno-docker
that referenced
this issue
Aug 11, 2021
Make does not work with alpine 3.14, this commit pins the alpine version to 3.13 to fix the issue. Fixes denoland#152
wperron
added a commit
that referenced
this issue
Aug 11, 2021
Make does not work with alpine 3.14, this commit pins the alpine version to 3.13 to fix the issue. The root cause seems to be [this issue][1] with Alpine and Docker 20.10.5 and earlier. How this issue presents itself in other container runtimes is unclear, but consensus seems to be that reverting to alpine 3.13 fixes the issue. [1] alpinelinux/docker-alpine#182 Fixes #152
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just spent a while headbutting weird CI failures. The ultimate solution was to rip apart and copy-paste
alpine.dockerfile
, but with the pinned version ofFROM frolvlad/alpine-glibc:alpine-3.13
. Because in this repo the dependency version is not pinned, newer images used3.14
which caused weird edge case breakage in our build.I'm not sure how this should be versioned. In our case, we want newer Deno but older Alpine. No specific recommendation here, just letting you know about the problem for now.
The text was updated successfully, but these errors were encountered: