[BUG] /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

[Lebon14]

Describe the bug
Start the container and stops after a few seconds with:
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

To Reproduce
Install using the (outdated) steps for Synology.
Try to start the Container...

Expected behavior
...It shouldn't stop after a few seconds?

Screenshots

speedtest-tracker HTML log.zip

Context

• OS: Containment Manager (Docker), DSM 7.2-64570 Update 1, Windows 11 Pro
• Speedtest-Tracker Version: latest

Additional context
Disclaimer: I actually hate anything that when I click "install" and doesn't work and somehow I'm expected to run command lines that are not documented or have knowledge on how to find said directory and other things I have zero idea about.
Also: it's said to use my IP but what IP? My public IP or my Synology IP? Anyway, it's not like it's working anyway.

I have forwarded the ports on my router as well.
Really, otherwise, I installed it like I was told...

[AlienPie]

This is not a bug, it is an error. It's clearly stated on the screen that the app is failing to connect to the database. I would check and confirm that the permissions on your /config directory align with the UID running the container. You can align these with the PGID and PUID variables, as documented.

[Lebon14]

This is not a bug, it is an error. It's clearly stated on the screen that the app is failing to connect to the database. I would check and confirm that the permissions on your /config directory align with the UID running the container. You can align these with the PGID and PUID variables, as documented.

I understood NOTHING of that.

If I remember correctly, I (tried to) followed the install guide as best as I could as they seemed out of date with the current version of Synology. The permissions are stock Synology as I ony ever use my NAS for my data and it backs itself up to Backblaze B2. If I rememer correctly, there was NO mention of ANY permissions. And why would it need extra permissions for SPEEDTESTS?!

Also, this ticket is 9 months old at the time I'm writing this. So, don't dunk on me cause something that released in the meant time that made things easier, documents got corrected, etc.

[AlienPie]

Not dunking, sorry!

I don't want to come across patronising so apologies if you know any of this. When a docker container runs, it runs like a process. That process runs as a user, which will have a userid and groupid attached to it (UID, GID).

On a NAS, your data stores are often owned by a user, and the permissions on the folder are set to allow a user, or group, access to read/write/execute in that directory.

If the directory which is being used to store the speedtest files (the one you map with -v, or whichever way synology does it) does not allow the user speedtest is running as (usually 1000 by default) to access it, then it will throw an error saying it's unable to access it. this is why we map in the environment variables UID and GID - these should match the owner of your directory.

This is why this would be considered not a bug, especially as the repo does not offer instructions to install on synology.

Not that it really matters as it seems this project is dead now :(