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
yarn
not found in node:alpine
#649
Comments
I'm seeing the same in circleci
|
I'm experiencing the same issue. |
Same here. |
Same for the normal
|
Same here with node:carbon |
This was caused by this commit: ae26d21 Given the way the symlink is done |
node:9.7-alpine image seems unaffected |
Seems to affect all supported tags except |
The problem is with |
The link /usr/local/bin/yarn is broken, it targets
|
Broke our CI as well this morning! |
Same here, with every version of node. We've already tried carbon and latest. Both fail with the yarn command. |
This affects |
@SimenB I volunteer to make a PR. I will remove the mkdir -p and replace by a symlink where the yarn has been decompressed. |
@cecton thanks! |
I will be able to fix that in several hours. If anyone can take care of it earlier, please do. |
I asked for a revert in docker-library/official-images#4131, but I think they are all on the west coast of the US, so probably asleep. |
Adding the following to my Dockerfile as a temporary fix helped. Remember YMMV! |
Reason is a change to `8.10.0` broke the image. See [issue](nodejs/docker-node#649) for more details.
Reason is a change to `8.10.0` broke the image. See [issue](nodejs/docker-node#649) for more details.
Close to finish.... |
Reason is a change to `8.10.0` broke the image. See [issue](nodejs/docker-node#649) for more details.
It's ok, I have a branch with the required changes. Will PR it in a minute. Will test locally as well. |
The image |
As @SimenB already written, image id is immutable identifier of the docker image, i. e. instead of
you should use
|
There's a good reason for tags not being immutable. One of the main benefit of Docker is that you inherit security fixes to underlying images. Sure there's a chance that a change to the base image might break a build but it's a trade-off that I personally gladly take to get the security benefits. |
Happening to our builds too...! |
@ojab as I wrote in my first comment, I am perfectly aware how to lock down a version. However, I find the use of “tag” misleading. In version control systems, a tag usually points to a given revision or commit (possibly on a specific branch). When a “tag” is updated, it is more like a VCS branch. The main problem with using the digest notation is that you don’t immediately see which tag it originated from. Other repositories as Maven, NPM, Yum, etc., contain versioned artifacts. I do not see why Docker should not. |
@LaurentGoderre There exist syntaxes for specifying that you want the latest version (at some level) for semver. But providing people the possibility to easily lock down the version would be nice. You never know when even a security patch breaks your production system. |
We are staying consistent with the other docker official images. Maybe there will be a solution to this issue in the future (in the form of a lockfile or something) |
Hey guys, thanks for the quick fix <3 That being said we continue having the problem when building our images :( |
You need to wait for the image to be published. It's currently being built |
@LaurentGoderre consistency is a good thing. :) Repeatable builds provides even better consistency. My comment is not limited to the node image. Where is the right place to raise this issue? |
I'm happy we were not the only one experiencing this issue 😅 , reverting to a earlier tag was our solution but kudos to the community on this form for providing suggestions. |
I think the whole world ended up here when they realized their builds were not passing lol! |
The fix seems to have made its way through the system. I've just had a GitLab CI build pass using the |
@SimenB @LaurentGoderre - PR with changes to prevent this sort of thing happening again - #658 |
I wrote up a blog post to explain how/why this happened, why it's not completely unexpected and can happen again, and what you can do to protect against it in future: https://renovateapp.com/blog/docker-mutable-tags In summary:
|
I believe there is a much simpler solution: if you use Docker for your work, host your own registry and update the images when you need to. |
@cecton no build time Internet is good for private projects, but not open source development. Also, it does not solve the problems with not having a repeatable build when debugging. |
That should read: “no build time Internet dependencies” |
Yes actually, you made a good point... I was more thinking about professional projects. |
Fixed by adding
from https://hub.docker.com/r/jfyne/node-alpine-yarn/dockerfile to my |
For me the issue was in using singlequotes in Dockerfile CMD command
|
I'm using the
node:alpine
image in a gitlab-ci build.Since a few minutes ago I get the following error in gitlab-ci:
My
.gitlab-ci.yaml
:The text was updated successfully, but these errors were encountered: