Startup error when http_host is set: Failed to start on port: 8090. Is something else running? about docker-mylar HOT 3 CLOSED

If you are are combining container networks they can conflict on the internal ports.
Something inside these docker networks is listening on 8090 and thus why it cannot bind to it , you can run something like

netstat -tunlap

inside your containers to determine what that could be.

In any case I appreciate the detailed information, but I do not believe this issue is a bug report of feature request specific to the Mylar container.
If you need further assistance please hop on our discord:

https://discord.gg/YWrKVTn

from docker-mylar.

As I noted in my note:

I have confirmed that nothing else is running on this port.

I can also change the port to other ports (18090 for example) in the config.ini file and the error message persists (updating the port listed to the configured value as well).

I should note: I have isolated this behavior on a machine with a fresh install of Ubuntu 18.04 server, docker installed per the docker websites getting-started guide. There are no other docker containers running on this machine presently.

I do not get this behavior if I just install mylar outside of docker on my local.

I do not, however, know what you mean when you say:

If you are are combining container networks they can conflict on the internal ports.

Is there something in my run command that I should adjust? As I noted, this is on a vanilla install of my stack.

from docker-mylar.

The general gist of my message is that this is really not the forum for support . You should not be changing the internal port for any reason.
We do test these images https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/mylar/latest/index.html and I have confirmed locally that it works.
So it has to be your local setup.
Please leverage our community on Discord it is possible someone has run into an issue like this before .

from docker-mylar.