By Monica Riccelli-Oracle on Jan 31, 2017
We are pleased to announce that the Oracle Container Registry is now available. The Container Registry is designed to provide simple access to Oracle products for use in Docker containers.
The Oracle WebLogic Server 188.8.131.52 and 184.108.40.206 images are now available on the Oracle Container Registry. Currently, access to the Oracle Container Registry is limited to customers in the United States, United Kingdom and Australia.
How do I login to the Oracle Container Registry?
Point your browser at https://container-registry.oracle.com. If this is the first time you’re visiting the Container Registry, you will need to associate your existing Oracle SSO credentials or create a new account. Click the “Register” button and select either: “I Already Have an Oracle Single Sign On Account” to associate your existing account or “I Don't Have an Oracle Single Sign On Account” to create a new account.
Once you have an account, click the login button to log into the Container Registry. You will be prompted to read and accept the license agreement. Note that acceptance of the license agreement is required to download images using the Docker command-line tool and that acceptance only persists for eight (8) hours.
After accepting the license, you can browse the available business areas and images to review which images you’d like to pull from the registry using the Docker client.
Pull The WebLogic Server images
The Oracle WebLogic Server images in the registry are install/empty domain images for WebLogic Server 220.127.116.11 and 18.104.22.168. For every version of WebLogic Server there are two install images one created with the generic installer and one with the quick installer. To pull the image from the registry run the command
# docker pull container-registry.oracle.com/middleware/weblogic
To create an empty domain with an Admin Server running, you simply call
# docker run -d container-registry.oracle.com/middleware/weblogic:22.214.171.124
The WebLogic Server image will invoke createAndStartEmptyDomain.sh as the default CMD, and the Admin Server will be running on port 7001. When running multiple containers map port 7001 to a different port on the host:
# docker run -d -p 7001:7001 container-registry.oracle.com/middleware/weblogic:126.96.36.199
To run a second container on port 7002:
# docker run -d -p 7002:7001 container-registry.oracle.com/middleware/weblogic:188.8.131.52
Now you can access the AdminServer Web Console at http://localhost:7001/console.
Customize your WebLogic Server Domains
You might want to customize your own WebLogic Server domain by extending this image. The best way to create your own domain is by writing your own Dockerfiles,and using WebLogic Scripting Tool (WLST) to create clusters, Data Sources, JMS Servers, Security Realms, and deploy applications.
In your Dockerfile you will extend the WebLogic Server image with the FROM container-registry.oracle.com/middleware/weblogic:184.108.40.206 directive.
We provide a variety of examples (Dockerfiles, shell scripts, and WLST scripts) to create domains, configure resources, deploy applications, and use load balancer in GitHub.