Running Weblogic 10.3 config utils in console mode, and gui mode in a Docker container

Most of Weblogic’s config utilities can run in a console/text mode if you need to run them from a terminal session in text mode, by passing the option: -mode=console

E.g. the apps here: /[middlewarehome]/wlserver_10.3/common/bin, like will run in console mode. however does not, and only runs in gui mode. This is an issue if you’re running Weblogic in a Docker container. All is not lost however, as you can forward X out of a Docker container, but it takes a few steps to get running.

Follow the steps in this logged issue to install and run socat, and then pass ‘-e DISPLAY=’ where the IP address is the address of the vbox interface.  On my Mac this looked like:

socat TCP-LISTEN:6000,reuseaddr,fork UNIX-CLIENT:\"$DISPLAY\"


docker run -it -e DISPLAY= imageid bash

My image included xterm and dependencies installed via the Dockerfile with:

RUN yum install -y xterm

When attempting to run in gui mode however, it gave me this error:

Unable to instantiate GUI, defaulting to console mode.

This is fine for at it runs in console mode, but since does not, it must run in gui mode with forwarded XWindows.

This post on ServerFault held the key – you need to also install libXtst:

yum install libXtst

Now all the utils will run in GUI mode forwarding X to your host. On Mac OS X this assumes also that you have XQuartz installed too.

Weblogic Portal 10.3.6 generic installer on Mac OS X – Insufficient Disk Space error

Trying to use the portal103_generic.jar installer on Mac OS X 10.11.1 gives this error even though you have plenty of free space:

A quick Google turns up this question and answer. Quick fix, run passing this option:, so:

java -jar portal103_generic.jar

Although others reported this avoided the issue, I then got this issue instead:

Exception in thread "chmodFile" java.lang.Error: Unix is not a supported OS platform.
 at java.lang.UNIXProcess$Platform.get(

Following additional suggestion here, using -Dspace.detection=false instead avoided the issue.

Connecting to the WildFly web admin console on OpenShift

OpenShift limits the ports that are publicly accessible from your running cartridges. To connect to the WildFly web console on port 9990, you can use the port forwarding:

rhc port-forward yourappname

When it reports the list of forwarded ports, connect to localhost:9990 and logon with your admin user/password.

More info here.