Portainer down yml obsolete

How to rescue my portainer got this error?

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/portainer.yml' --file "/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/compose.override.yml" --env-file '/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/global.env' --env-file '/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/portainer.env' up -d  2>&1': time="2025-03-05T00:12:17-08:00" level=warning msg="/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/portainer.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
unable to get image 'portainer/portainer-ce:latest': Error response from daemon: layer does not exist

OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; docker compose --file '/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/portainer.yml' --file "/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/compose.override.yml" --env-file '/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/global.env' --env-file '/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/portainer.env' up -d  2>&1': time="2025-03-05T00:12:17-08:00" level=warning msg="/srv/dev-disk-by-uuid-1942e416-bbf4-4f33-b6a3-00171f82bf75/compose/portainer/portainer.yml: the attribute `version` is obsolete, it will be ignored, please remove it to avoid potential confusion"
unable to get image 'portainer/portainer-ce:latest': Error response from daemon: layer does not exist in /usr/share/openmediavault/engined/rpc/compose.inc:970
Stack trace:
#0 /usr/share/php/openmediavault/rpc/serviceabstract.inc(622): OMVRpcServiceCompose->{closure}()
#1 /usr/share/openmediavault/engined/rpc/compose.inc(937): OMV\Rpc\ServiceAbstract->execBgProc()
#2 [internal function]: OMVRpcServiceCompose->doCommand()
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(122): call_user_func_array()
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod()
#5 /usr/sbin/omv-engined(544): OMV\Rpc\Rpc::call()
#6 {main}

This is not working, I commented it out, and got something about unable to get image layer does not exist?

Never mind, after reboot I was able to pull portainer up

TKS

Well not resolved yet now Portainer came with only one container itself the stacks was still in there I was able to pull home assistant but all the other one cannot get image or layer does not exist!

Quote from raulfg3

ghcr.io have some acess troubles, try deleting ghcr.io/

eg: haveagitgat/tdarr:latest

Cool, but where do I find it?

And on another one is layer does not exist!

Need help with compose I removed it installed it again same error cannot pull any image layer does not exist?

So I had enough I completely rm var/lib/docker I just had to ssh docker network create swag_default since some containers could not be recreated and they were giving me "Failed to deploy a stack: compose up operation failed: Error response from daemon: failed to set up container networking: network swag_default not found" the lat one make me pull my hair for some time

Well is getting complicated this morning after reboot most of the container disappeared I was able to put one or two up but after that got again layer does not exist!

I tried again new docker install but does not matter even a brand new portainer just downloaded from compose file I am able to have a container working emby as example) but after a reboot the containers is gone except portainer the strange thing, as soon as I downloaded portainer it was down impossible to put it up since OMV said it did not exist but after reboot it was working except the main issue not keeping container after subsequent update go figure!

In fact I found out, If I

\ reinstall docker the container came back so what should I do knowing my docker is on /srv/dev-disk-by-uuid-9cd27ed0-ef9a-4346-ae1e-5e835ba05832/Media2/docker ?

I think my problem is volumes in portainer because I cannot find any but volumes are defined in my stacks but again cannot

Failed to deploy a stack: compose up operation failed: unable to get image 'linuxserver/emby:beta': Error response from daemon: layer does not exist

Update emby beta is down, but I am not gonna use the non beta since the database is not compatible between both and I am not gonna rebuilt it now available at https://hub.docker.com/r/emby/embyserver

Basically and to make it short! After reboot portainer show no containers except itself until I restart docker and then everything come back but still no volumes listed in portainer?

I do not have a dns but a gateway ! When I told you my OMV is sick it is even sicker I got a disk to repair but although I unmounted it says disk in use

umount -f /dev/sdc
umount: /dev/sdc: not mounted.
root@openmediavault:~# fsck.ext4 -f /dev/sdc
e2fsck 1.47.0 (5-Feb-2023)
/dev/sdc is in use.