Closed dr460nf1r3 closed 5 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Can you docker pull linuxserver/nextcloud:27.1.1
and then rerun docker-compose up -d
[root@docker:/var/garuda/docker-compose-runner/all-in-one]# docker pull linuxserver/nextcloud:27.1.1
27.1.1: Pulling from linuxserver/nextcloud
253722c5a7d8: Extracting [==================================================>] 5.63MB/5.63MB
07a0e16f7be1: Download complete
f93399c9350d: Download complete
76fb3bb5b225: Download complete
7bb40d29e696: Download complete
bb4474cecf2a: Download complete
2c651e8d9fb8: Download complete
b9421bbf9836: Download complete
d77cfece025b: Download complete
failed to register layer: operation not permitted
Sadly also failing with the same error message.
[root@docker:/var/garuda/docker-compose-runner/all-in-one]# docker pull linuxserver/nextcloud:27.1.1 27.1.1: Pulling from linuxserver/nextcloud 253722c5a7d8: Extracting [==================================================>] 5.63MB/5.63MB 07a0e16f7be1: Download complete f93399c9350d: Download complete 76fb3bb5b225: Download complete 7bb40d29e696: Download complete bb4474cecf2a: Download complete 2c651e8d9fb8: Download complete b9421bbf9836: Download complete d77cfece025b: Download complete failed to register layer: operation not permitted
Sadly also failing with the same error message.
Sorry for the delayed response. This does not look like an issue with the image. It could possibly be a connectivity or DNS issue, or an issue with a specific registry. Here are some alternatives you can try:
docker pull lscr.io/linuxserver/nextcloud:27.1.1
docker pull ghcr.io/linuxserver/nextcloud:27.1.1
docker pull quay.io/linuxserver.io/nextcloud:27.1.1
docker pull registry.gitlab.com/linuxserver.io/docker-nextcloud/nextcloud:27.1.1
If any one of those work then you can use that in your compose. If none of them work then I would recommend trying to pull another image of ours to see if it's specific to nextcloud.
Sorry for the delayed response
Np, I'm guilty of it too!
If none of them work then I would recommend trying to pull another image of ours to see if it's specific to nextcloud.
Sadly all of them failed so I proceeded to try other ones:
[root@docker:~]# docker pull linuxserver/nginx
Using default tag: latest
latest: Pulling from linuxserver/nginx
a43e029ba662: Extracting [==================================================>] 5.63MB/5.63MB
07a0e16f7be1: Download complete
e3303cebae64: Download complete
35c9530ef606: Download complete
693b3eff61d8: Download complete
61906b476bf9: Download complete
505ce5c161b3: Download complete
86680f0a4aaf: Download complete
failed to register layer: operation not permitted
Same thing here:
[root@docker:~]# docker pull linuxserver/sqlitebrowser
Using default tag: latest
latest: Pulling from linuxserver/sqlitebrowser
a43e029ba662: Extracting [==================================================>] 5.63MB/5.63MB
07a0e16f7be1: Download complete
e3303cebae64: Download complete
35c9530ef606: Download complete
693b3eff61d8: Download complete
8f2dc51c48c4: Download complete
a88172b3d190: Download complete
8d1dc2303fd5: Download complete
90d408ea59dc: Download complete
dea2770dbc14: Download complete
ec46e0fd650f: Download complete
failed to register layer: operation not permitted
But I found one working among the ones I tried:
[root@docker:~]# docker pull linuxserver/sonarr:latest
latest: Pulling from linuxserver/sonarr
f83c38a97647: Pull complete
07a0e16f7be1: Pull complete
2f5368079c48: Pull complete
727f1a78792f: Pull complete
472bb230a37d: Pull complete
1141a882de05: Pull complete
c61c25f07bd5: Pull complete
bf12357cc297: Pull complete
Digest: sha256:296e553380b1b5d32be623ce2b97f67b69fc57449b9ef07195baa6a5df2b9bd6
Status: Downloaded newer image for linuxserver/sonarr:latest
docker.io/linuxserver/sonarr:latest
Hope this might give some ideas. As I said, every other image we run on the same server (lots) is working just fine.
Could be something related to nixOS, I'm not seeing reports for any other distro.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
This issue is locked due to inactivity
Is there an existing issue for this?
Current Behavior
Newer versions of the container (>27.0.1.2) can't be pulled successfully anymore, failing with:
Since older versions (exemplary
27.0.1.2
) are still getting pulled correctly and all other containers on this server also don't act up like that, I suspect something in the image is not working as expected.I sadly also can't use the older working image due to a mismatch of versions:
The existing images and layers had already been cleared before creating this issue - one time via
docker system prune -a
and another time via completely wiping/var/lib/docker
.Following the output of
docker info
:I'd appreciate help, even if it's just a hint on getting the older image to work with the newer data version. Thanks, also for providing and maintaining this image! 😊
Expected Behavior
The image can be pulled successfully.
Steps To Reproduce
I suppose you could try pulling the image with the config used:
Environment
CPU architecture
x86-64
Docker creation
The config we were using before the breakage occurred can be found here.
Container logs
No logs are available since the error occurs while pulling the image.