After a couple of reboots I'm still getting execution error 403.

 

Attached are diagnostics from a recently restarted server.

morn-diagnostics-20240206-2117.zip

i might remember that issue, i think it was something with the docker.image file

you may try to stop /disable docker

move or backup the docker image file, can see the location under "Docker vDisk location:" in settings/docker

 

than start to enable docker again

all containers will be gone, you can add them with add one by one, settings should be saved, so its just a click add, save and wait to redownload image

 

if it does not work for the first container, you can delete the new docker file, and rename the backuped , so nothing to loose

13 hours ago, astronax said:

you can add them with add one by one, settings should be saved,

You only get the saved settings if you use Apps->PreviousApps

23 minutes ago, itimpi said:

You only get the saved settings if you use Apps->PreviousApps

Sorry that is Not true, you can Go to docker tab, add Container, select User Templates and find all old Templates.

Have done that multiple Times, and was Happy about this

10 minutes ago, astronax said:

Sorry that is Not true, you can Go to docker tab, add Container, select User Templates and find all old Templates.

Have done that multiple Times, and was Happy about this

Ok - that is the long way around in my opinion.    Going via Apps->Previous Apps does this more conveniently I think and is functionally equivalent..

Deleted the entire vdisk. No problem to start containers after that. Hopefully it will stay that way. Thanks

 

Edit:
RIP Immich (due to docker-compose I guess).

Edited February 8, 20242 yr by shunde