TCP/IP connections about docker-galaxy-stable HOT 8 CLOSED

@jjkoehorst you need to use the startup script. We need to start a lot more than Galaxy. The webserver for example, a scheduler ....

from docker-galaxy-stable.

Indeed see that now, as I didn't see the startup.sh script in the docker I assumed I needed the galaxy run.sh.

Now running the startup script line by line to see what is happening.

I do get an nodejs proxy error, trying to figure out what it means.

Starting ProFTP
proftpd: started
Starting Galaxy reports webapp
reports: started
Starting nodejs
galaxy:galaxy_nodejs_proxy: ERROR (abnormal termination)

from docker-galaxy-stable.

nodejs should not be the problem. Are you running on OS-X or Windows.

from docker-galaxy-stable.

Running OS-X but I thought the idea of docker was that it is independent of the OS like a virtual machine or is something else going on?

from docker-galaxy-stable.

Yes it is. But you will get a different IP address on OS-X because it get's routed through a VM and from the VM to Docker. This is usually a problem that our users encounter on OS-X.

from docker-galaxy-stable.

Yes indeed that IP address is an "issue"...

Now trying to work with

CID=$(docker run -d -p 8080:80 -p 8021:21 bgruening/galaxy-stable);
docker inspect --format '{{ .NetworkSettings.IPAddress }}' ${CID}

And use that IP address to access galaxy

Recon that, using Kitematic (beta) it starts up as a charm!

from docker-galaxy-stable.

You can try kitematic, this might be easier for OS-X user.
Let me know if you have more problems. Can we close this issue?

from docker-galaxy-stable.

Yes I think we posted and edited at the same time. Case closed

from docker-galaxy-stable.