Binding address for WildFly deployment

What I learned today — 26 July 2018

After launching a WildFly server in standalone mode running in Docker by following the instructions on DockerHub I was completely baffled to see this message when trying to connect to the service endpoint:

curl: (56) Recv failure: Connection reset by peer

It turns out, you need to explicitly set the bind address for the server to listen on. Setting it for the management interface only is not sufficient. Start the server like this:

docker run -p 8080:8080 -p 9990:9990 -it jboss/wildfly /opt/jboss/wildfly/bin/standalone.sh -bmanagement=0.0.0.0 -b 0.0.0.0

This will let the server listen on port 8080 and 9990 (where the management console runs) on all interfaces.