-
-
Notifications
You must be signed in to change notification settings - Fork 371
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
Error on automation with Docker Hub but not when running manually #378
Comments
I can't replicate this issue. Also the tests executed by GitHub Actions work without issues. Did you try to re-build your docker image? Maybe it was a transient issue? Without being able to reproduce it, I can't understand what may be going wrong. |
I have same problem when build on docker hub:
My Dockerfile:
Issue replicate only on docker hub (local build work fine) for |
It seems a docker hub issue: https://forums.docker.com/t/multiple-projects-stopped-building-on-docker-hub-operation-not-permitted/92570 There's really nothing I can do |
So this sounds like it is a coreutils/host kernel problem. Unfortunately this is happening with the blessed version of PHP 7.4 on Alpine, php:7.4-fpm-alpine, which is heavily in use. |
@mlocati Thanks for pointing me in the right direction, I pinned to @doanbaanh You might want to adjust your Dockerfile to pin as well. |
Same issue in GitLab CI. There's something funky about these newer versions of Alpine. Edit: |
Really strange that this has been noticed since April/May last year but it's only affecting these images now, though. 🤔 Either way, it sounds like GitLab needs to sort this out too. I indeed could build these images locally but see the same error in GitLab CI pipelines run in the shared GitLab runners. |
Not so strange: only alpine 3.14 seems to be affected (maybe because it's using the coreutils version that's incompatible with the Docker Hub build systems) |
And the Alpine 3.14 PHP images are made available since docker-library/php#1166 |
Ah right, I thought they would have been using 3.14 sooner than a month ago. Fair enough. 👍 |
I'm closing this issue, since it's related to the statx-related features introduced in the coreutils version available in Alpine Linux 3.14 (and probably in Debian 11 - Bullseye), which don't work if the host machine is running an old kernel version. |
It is working again in Alpine 3.15. In my Dockerfile I replaced this: # We use alpine 3.13 because there is a bug on installing PHP extensions on 3.14
# See https://github.com/mlocati/docker-php-extension-installer/issues/378
FROM php:8-fpm-alpine3.13 as php-fpm with: FROM php:8.1-fpm-alpine as php-fpm This would not have worked with 3.14 but on 3.15 it is working again. |
I have an automated build for when new versions of PHP come out. It is based on the php:7.4-fpm-alpine image which currently uses Alpine 3.14.0 and PHP 7.4.21. Here is my Dockerfile.
On our automated build, it appears that igbinary having an issue:
As I said, this is not happening when running manually.
Do you think that Docker Hub could be caching an old image or Github version of docker-php-extension-installer?
From the build.log it does look like it is using docker-php-extension-installer v.1.2.39.
The text was updated successfully, but these errors were encountered: