I created a new container yesterday without issues, today I can't start it anymore. I created two new clean containers, most of the times it crashes upon launch, and yet sometimes it actually launches successfully:
*** Running /etc/my_init.d/30_update.sh...
error: cannot open .git/FETCH_HEAD: Permission denied
*** /etc/my_init.d/30_update.sh failed with status 1
*** killing all processes...
or this one
*** Running /etc/my_init.d/30_update.sh...
Cloning into '/app/couchpotato'...
fatal: Could not read from remote repository
Please make sure you have the correct access rights
and the repository exists.
/etc/my_init.d/30_update.sh: line 7: /app/couchpotato: No such file or directory
fatal: Not a git repository (or any of the parent directories): .git
*** /etc/my_init.d/30_update.sh failed with status 128
*** killing all processes...
The next time it launched fine (?) so I shut it down for further testing. Got the first one again after that.
Different clean container, started with the first error. Next time it seemed to get a bit further but alas:
*** Running /etc/my_init.d/30_update.sh...
Cloning into '/app/couchpotato'...
remote: Counting objects: 49208, done.[K
remote compressing objects: 7% (1/13) [K
Receiving objects: 0% (1/49208)
Receiving objects: 100% (49208/49208), 20.64 MiB | 2.26 MiB/s
Resolving deltas: 0% (0/29554)
Checking connectivity... done.
fatal: Could not read from remote repository
Please make sure you have the correct access rights
and the repository exists.
*** /etc/my_init.d/30_update.sh failed with status 1
*** killing all processes...
the next launch it launched fine, so I shut it down again! Next launch booted fine, most like due to it thinking it's up to date:
But then I shut it down again and now it seems to always fail with:
*** Running /etc/my_init.d/30_update.sh...
fata: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
*** /etc/my_init.d/30_update.sh failed with status 1
*** killing all processes...
Anybody have an idea of what is going on and how to fix this?
Using a Synology DS1813+ DSM 6.0-7321
I created a new container yesterday without issues, today I can't start it anymore. I created two new clean containers, most of the times it crashes upon launch, and yet sometimes it actually launches successfully:
or this one
The next time it launched fine (?) so I shut it down for further testing. Got the first one again after that.
Different clean container, started with the first error. Next time it seemed to get a bit further but alas:
the next launch it launched fine, so I shut it down again! Next launch booted fine, most like due to it thinking it's up to date:
But then I shut it down again and now it seems to always fail with:
Anybody have an idea of what is going on and how to fix this?