-
Notifications
You must be signed in to change notification settings - Fork 2k
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
image arm32v7/node:13.6-slim not working #1195
Comments
Does it occur if you use the non-slim version? If it doesn't, then it's likely related to #1182 |
it does not occur in the non-slim version. |
You'll probably need to apt-get install the needed dependencies or switch to the non-slim version. The PR removed packages that aren't normally shipped on slim images |
I was expecting that a node image can perform a
|
Yeah, none of the ARM stuff is tested as part of this repo, just cross-built as part of the Official Images repo setup. @tianon does the BATS tests get run as part of that CI? |
The package |
@khassel these packages are side-effects that shouldn't have been there in the first place. |
None of our build/test process runs any of the BATS tests from this repository. We have a minimal set of tests (https://github.com/docker-library/official-images/tree/master/test) which we run as part of smoke-testing PRs to https://github.com/docker-library/official-images, but they're too much overhead for us to run on every published artifact (and frankly, for some of those tests the fact that they fail does not necessarily mean the artifact should not be published).
I'm not sure that's completely accurate if This is why in #1182 (comment) I linked to the potentially more-complicated version which also uses |
looks as node v13.6 needs |
Possibly related nodejs/node#30174 |
Since updating from v13.5 to v13.6 the image
arm32v7/node:slim
fails starting.Example:
docker run -it arm32v7/node:13.6-slim
results inThe text was updated successfully, but these errors were encountered: