Closed pjpscriv closed 6 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Use a Linux file path inside wsl for the config folder
That did the trick! :) I was using Hyper-V. Switching to WSL removed the error and smokeping is now up and running and collecting data.
Thanks @aptalca š
Is there an existing issue for this?
Current Behavior
When attempting to run the smokeping container on my 64-bit Windows 11 mini PC (full spec) through
docker compose
I get this error:Visiting https://localhost:8080/smokeping shows the same error through the web UI:
Solutions Attempted
1. Change file access permissions on the host system
I tried modifying the windows security settings of
D:\dev\smokeping\config\smokeping_secrets
: Properties -> Security and Denying all permissions for the Everyone group as below:This produced a new error:
2. Change file access permissions inside the container
I then tried opening a terminal in the container and running a command found from a smokeping forum post working with the same error message. This didn't seem to have an impact on the file's access permissions.
Terminal commands / outputs:
The same is true for trying to run
chmod
against/config/smokeping_secrets
:3. Add a startup command to the docker-compose.yml
Then I tried adding the
chmod
command into the docker compose file using the command but I suspect I'm misusing this field.And indeed this setup didn't work. The container simply stopped after some of the startup messages (IIUC because I'm overwriting the default startup command š ).
Expected Behavior
Container start and run normally
Steps To Reproduce
docker-compose.yml
as documenteddocker compose up
Environment
CPU architecture
x86-64
Docker creation
Container logs