Closed ghost closed 9 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.
You did not map any ports. Either map the ports, or run with host networking.
Closing, not a bug.
When I initially sought out support via Discord, I was told that port mapping didn't matter because the container ran in host mode (the logs will even warn that mapped ports will be ignored). Additionally, I was advised to set it to bridge mode in an attempt to access the web UI. If I set it back to host, I get an identical log.
Could this issue please be reopened?
Please continue seeking support on discord. GitHub is for bug reports.
Is there an existing issue for this?
Current Behavior
I'm unable to access the web UI for Owntone at http://owntone.local:3689/ or http://ip:3689/ despite the container running. As the container starts, there are numerous fatal errors for mDNS failing to initialize, but eventually the container appears to start normally. I'm not sure if it matters, but I'm also running networks for Caddy and Gluetun on the same server. Stopping both containers does not resolve the issue or change the log.
Note that I had to trim the log down to fit within the character limit. The initialization message listing all the services and mDNS failing to init was listed dozens of times.
Expected Behavior
Owntone should be accessable at http://owntone.local:3689/ or http://ip:3689/.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation