-
Notifications
You must be signed in to change notification settings - Fork 267
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
alpine:latest can not reach outside #151
Comments
same problem!!! I've armv7 `dietpi@hass:~/alpine$ sudo docker run busybox ping -c 3 192.203.230.10 --- 192.203.230.10 ping statistics --- --- 192.203.230.10 ping statistics --- |
Let me close this one in favor of #155 |
i suspect this is due to the time64 change in recent musl libc, in combination with the libseccomp/docker issue. It should work if you have either:
|
As @ncopa alludes to, this issue appears to manifest on older versions of certain Linux distributions. In my case, I was running an older version of Raspbian (10; Buster) and was able to resolve the issue by upgrading libseccomp2 and Docker on the host like so:
Prior to upgrading, I was seeing the following errors from within an Alpine 3.18 container:
Note the older version of Raspbian on the host:
After upgrading using the script above, the Alpine 3.18 container on the Raspbian 10 (Buster) host works as expected:
|
For the second time in a row we bite our tails on:
This happens when we use actions like this:
https://github.com/anothrNick/github-tag-action/blob/master/Dockerfile
I already committed a PR but I wonder. Why does latest
alpine
not work.As soon as one switches to
alpine:3.10
it suddenly works. Why?Is this already known? If wanted I can try to reproduce with public actions (as our SAP ones are not public)...?
The text was updated successfully, but these errors were encountered: