-
|
I try to launch a container on my truenas server with portainer. I spend so much hours on this issue and I'm still stuck at the same point. I test a lot of differents parameters but for this example I've created a stack with the following compose. I test so much things but this is a list of what I've test :
I'm stuck since a long time so this is my last chance ComposeError |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
The error Permission denied while trying to execute ./FactoryServer.sh indicates a file permissions issue. Even though you’ve used chmod 777 FactoryServer.sh, the issue might still persist due to how the file is being accessed in the containerized environment. Let’s troubleshoot step by step:
Ensure the volume ./satisfactory-server:/config is correctly mounted and accessible within the container. Run the following commands: docker exec -it satisfactory-server bash ls -l /config Verify that the file is present and has executable permissions (-rwxrwxrwx or similar).
The container runs as the user defined by PUID and PGID. Check the ownership of the files in the mounted directory: ls -l sudo chown -R 3000:3000 ./satisfactory-server
Set ROOTLESS=false in your docker-compose.yml file and redeploy the stack. Some permissions may not propagate correctly when ROOTLESS=true.
If your TrueNAS server has SELinux enabled, it may block Docker from accessing the mounted files. To test: setenforce 0
Sometimes cached settings or files can cause issues. Rebuild the container: docker-compose down
If the issue persists, you can manually test running the script: docker exec -it satisfactory-server bash cd /config sh FactoryServer.sh
If the issue is related to how Docker mounts the volumes, try using absolute paths instead of relative paths: volumes:
Check Docker logs for additional details: docker logs satisfactory-server Final Step: If All Else Fails Try running a minimal container with only the shell to test the permissions and script execution: docker run -it --rm -v $(pwd)/satisfactory-server:/config ubuntu:latest bash This will help isolate whether the issue is with the Docker setup or the application container. |
Beta Was this translation helpful? Give feedback.
-
|
I take time to recheck all of what you've said.
|
Beta Was this translation helpful? Give feedback.
-
|
@TaT5cher per my answer, see #378. It's likely an issue with your host filesystem. |
Beta Was this translation helpful? Give feedback.
-
|
Please see #378 |
Beta Was this translation helpful? Give feedback.
Please see #378