Parity-ethereum: Access parity v.1.5.2 in docker container

[vincentserpoul]

macosX
Docker 1.13 (no more docker machine, docker accessible on 127.0.0.1 forwarded ports)
ethcore/parity:v1.5.2

even though the ports are published, parity wouldn't allow connection on 127.0.0.1:8180 or 127.0.0.1:8080.

I tried the --ui-no-validation but still the same thing.

Any idea?

[vincentserpoul]

This makes the whole docker experience useful only to run a public node without any interaction with it, which kind of hide all the nice work done around Parity.

[tomusdrw]

What kind of errors do you get? Could you post the commands you used to start the docker container?

[tomusdrw]

Parity by default listens only on localhost interface, probably you need to expose bind to external IPs of the container as well.

[vincentserpoul]

The most simple run I can do is:

docker run -dit --name testparity -p 8180:8180 -p 8080:8080 -p 8545:8545 ethcore/parity:v1.5.3

On mac, Docker publishes ports on localhost, so it should be exactly like the default config.

Is anybody running a ethcore/parity:v1.5.3 container and accessing the UI?
If yes, could you post your config?

[tomusdrw]

Could you try altering CLI parameters (or create a config file) and set --ui-interface 0.0.0.0 --ui-no-validation --dapps-interface 0.0.0.0 --dapps-hosts all?

Afair you need to listen on docker external interface for any port publishing to work.

[vincentserpoul]

@tomusdrw just tried on linux and tested each params.
The --ui-interface 0.0.0.0 is the one needed to access the parity UI.
I'm not sure why it's not needed on the non containerized parity though.

I will test on a mac to confirm in a few hours.

[tomusdrw]

So container has it's own localhost interface, to which parity is binding to. It's different than the host localhost interface.
You can use port-forwarding in docker, but it exposes a service listening to external interface of your container and makes it available on localhost of the host.

[vincentserpoul]

for mac: --ui-interface 0.0.0.0 --ui-no-validation worked too.

In the config file, I just added

force = true
interface = "0.0.0.0"

and I can reach my node on http://0.0.0.0:8180!

[dcorking]

Please add Vincent's finding to the wiki: https://github.com/paritytech/parity/wiki/Docker . The parity UI doesn't work (ERR_EMPTY_RESPONSE) on Mac OS X Docker without --ui-interface 0.0.0.0.

(Tested with Parity/v1.5.13-stable-69efb27-20170612/x86_64-linux-gnu/rustc1.16.0 on OS X El Capitan 10.11.6 (15G1510) Docker version 17.06.0-ce, build 02c1d87 docker-machine version 0.12.0, build 45c69ad)

[tomusdrw]

@dcorking Updated, thanks!