WildFly Admin Console in a Docker image (Tech Tip #67)

WildFly Docker image binds application port (8080) to all network interfaces (using -b If you want to view feature-rich lovely-looking web-based administration console, then management port (9990) needs to be bound to all network interfaces as well using the shown command:

This is overriding the default command in Docker file, explicitly starting WildFly, and binding application and management port to all network interfaces.

The -P flag map any network ports inside the image it to a random high port from the range 49153 to 65535 on Docker host. Exact port can be verified by giving docker ps command as shown:

In this case, port 8080 is mapped to 49161 and port 9990 is mapped to 49162. IP address of Docker containers can be verified using boot2docker ip command. The default web page and admin console can then be accessed on these ports.

Accessing WildFly Administration Console require a user in administration realm. This can be done by using an image which will create that user. And since a new image is created, the Dockerfile can also consume network interface binding to keep the actual command-line simple. The Dockerfile is pretty straight forward:

This image has already been pushed to Docker Hub and source file is at github.com/arun-gupta/docker-images/tree/master/wildfly-admin.
So to have a WildFly image with Administration Console, just run the image as shown:

Then checked the mapped ports as:

Application port is mapped to 49165 and management port is mapped to 49166. Access the admin console at which will then prompt for the username (“admin”) and the password (“Admin#007”).


If you don’t like random ports being assigned by Docker, then you can map them to specific ports as well using the following command:

In this case, application port 8080 is mapped to 8080 on Docker host and management port 9990 is mapped to 9990 on Docker host. So the admin console will then be accessible at

Be Sociable, Share!
  • Tweet

6 thoughts on “WildFly Admin Console in a Docker image (Tech Tip #67)

  1. Pingback: Javalobby - The heart of the Java developer community: Java EE, Docker, WildFly and Micros... - Java吧
  2. Pingback: JBoss on Docker At a Glance | Red Hat Developer Blog
  3. hi arun, your post is great….. i want to ask you something…. when i deploy a war file in admin console the container automatically exit and the server.log file show that the problem is duplicate resource, i dont know how to resolve it and i expect that you can help me 😀 , regards

Leave a Reply

Your email address will not be published. Required fields are marked *