Error starting in Synology - Docker #291
-
|
First off I wanted to thank you for all the time and effort put into this. I've been successfully using v2 of p2g in a docker container on my Synology NAS. I'm using the examples of both api.local.json and webui.local.json found in master/docker/webui/ without any changes. The changes made to the example docker-compose-ui.yaml were exposing port 8001:80 for p2g-api and updating the volume paths for my NAS when creating the stack. I initially tried to use the same volumes for app/data and app/output as v2, but created a new directory on the NAS to attempt to start fresh. Both attempts had the same errors. Here's a copy of the log and error. I assume the culprit is the Unhandled exception. System.IO.IOException: Failed to bind to address http://localhost:80. Any suggestions? Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
I agree this is the primary problem. I know Synology has support for managing containers via a GUI and docker-compose. On the Could you check what the current state is of that setting, and whatever it currently is, try toggling it to the other value and seeing if the error changes at all. Edit: Answer near bottom of the thread. |
Beta Was this translation helpful? Give feedback.
-
Hmmm yeah you're still hitting some kind of permissions issue, either imposed by Portainer or Synology. I'm also gonna work on a fix to clean up that |
Beta Was this translation helpful? Give feedback.
-
|
In an attempt to take Portainer out of the equation, I deleted the stack, uploaded a docker-compose yaml, ssh'd in and ran I'm trying to dig around on what could cause this. Is this at all helpful? Thanks again! |
Beta Was this translation helpful? Give feedback.
-
|
Yeah I'd been reading through that thread (and a couple others). While it makes sense, I'm still confused why I can't reproduce on my end since the Docker images should be identical. Regardless, I've made a couple changes, and you should be able to adjust the host and port P2G binds to. Give the below changes a try.
version: "3.9"
services:
p2g-api:
container_name: p2g-api
image: philosowaffle/peloton-to-garmin:api-latest
environment:
- TZ=America/Chicago
ports:
- 8001:8080
volumes:
- /volume1/docker/config/p2g/api.local.json:/app/configuration.local.json
- /volume1/docker/config/p2g/data:/app/data # recommended for saving settings across restarts
- /volume1/docker/config/p2g/output:/app/output # optional, if you want access to the generated workout and log files
p2g-webui:
container_name: p2g-webui
image: philosowaffle/peloton-to-garmin:webui-latest
ports:
- 8002:8080
environment:
- TZ=America/Chicago
volumes:
- /volume1/docker/config/p2g/webui.local.json:/app/configuration.local.json
depends_on:
- p2g-api
{
"Api": {
"HostUrl": "http://*:8080"
},
"Observability": { < your existing config> }
}
{
"Api": {
"HostUrl": "http://p2g-api:8080"
},
"WebUI": {
"HostUrl": "http://*:8080"
},
"Observability": { < your existing config> }
} |
Beta Was this translation helpful? Give feedback.
-
|
BINGO! That did the trick. So aside from the |
Beta Was this translation helpful? Give feedback.
-
|
Yay, so glad it worked! And yes, it seems port 80 was the culprit. The P2G process inside the container itself does not run as root. Its possible your other containers that use 80 are running their processes as root within the container. However, this does not explain why I can't reproduce the issue. Still thinking on that one. |
Beta Was this translation helpful? Give feedback.
I agree this is the primary problem. I know Synology has support for managing containers via a GUI and docker-compose. On the
General Settingspage I think there is a toggle forExecute container using high privilege.Could you check what the current state is of that setting, and whatever it currently is, try toggling it to the other value and seeing if the error changes at all.
Edit: Answer near bottom of the thread.