2024-08-15, 06:12 AM
(This post was last modified: 2024-08-15, 06:20 AM by Eisbergsalat. Edited 1 time in total.)
Soooooo..
I..
- downgraded to version 9 - no difference (went back to :latest)
- changed the docker daemon.json experimental from true to false - no difference (Dont even know why I did That! Found that thanks to "journalctl -xu docker.service")
- fixed a DNS Error for the docker resolver - no difference obviously, if docker cant reach the Internet, the containers can still reach it. But the log shouldnt get used as garbage again (Also thanks to "journalctl -xu docker.service")
- Found out, that Nextcloud doesnt start right away because of Mounting-Problems. But thats soemthing NC tells me in the Windows-client every 5 damn minutes ... WiP but not relevant for this
- Get a lot of "ShouldRestart failed, container will not be restarted" container=... But that is before shutdown and the other listed containers startup as usally after the reboot.
- I also changed the chmod so that everyone can run the docker compose. (chmod a+x...)
I dont know why I cant copy the log from Putty at the moment... If I can, I will post it later.
Currently I am using a rather unwanted fix:
I created the "JellyfinStartup.sh" in the same folder as the docker compose file
and in crontab -e
At the End of September I will be able to focus more on this, as the deadline of my Uni assignement ist at the beginning of Sep and the corresponding oral exam is at the end of Sep.
Edit:
Found out why I couldnt copy, it was an other programm with an invisible error message
I didnt try out the new .sh fix yet, so I will post the logs tomorrow.
Hopefully without as much clutter as I had till today
I..
- downgraded to version 9 - no difference (went back to :latest)
- changed the docker daemon.json experimental from true to false - no difference (Dont even know why I did That! Found that thanks to "journalctl -xu docker.service")
- fixed a DNS Error for the docker resolver - no difference obviously, if docker cant reach the Internet, the containers can still reach it. But the log shouldnt get used as garbage again (Also thanks to "journalctl -xu docker.service")
- Found out, that Nextcloud doesnt start right away because of Mounting-Problems. But thats soemthing NC tells me in the Windows-client every 5 damn minutes ... WiP but not relevant for this
- Get a lot of "ShouldRestart failed, container will not be restarted" container=... But that is before shutdown and the other listed containers startup as usally after the reboot.
- I also changed the chmod so that everyone can run the docker compose. (chmod a+x...)
I dont know why I cant copy the log from Putty at the moment... If I can, I will post it later.
Currently I am using a rather unwanted fix:
I created the "JellyfinStartup.sh" in the same folder as the docker compose file
Code:
docker compose down
sleep 60
docker compose up -d
and in crontab -e
Code:
45 2 * * * ....JellyfinStartup.Sh...
At the End of September I will be able to focus more on this, as the deadline of my Uni assignement ist at the beginning of Sep and the corresponding oral exam is at the end of Sep.
Edit:
Found out why I couldnt copy, it was an other programm with an invisible error message
I didnt try out the new .sh fix yet, so I will post the logs tomorrow.
Hopefully without as much clutter as I had till today