Due to setup issues (probably related to insufficient RAM) I have rebuilt the setenv.sh and docker-compose.yaml files to a format that makes more sense to me. See below for full code.
You can most likely use the default sample files from Oracles repo (docker-images/OracleIdentityGovernance/setenv.sh, and docker-images/OracleIdentityGovernance/samples/containerizedDB/docker-compose.yaml) to achieve the same result.
With my configuration you must add kiot.dev.local 172.30.0.1 and oimdb.dev.local 172.30.0.2 to /etc/hosts.
Start environment
The environment is very sensitive and must be started in correct order as the containers are dependant of each other. Either tweak the docker-compose.yml to wait, or start the containers manually and observe the status using docker logs -f <container-name>. Starting the containers will take several minutes.
Important: You must use the same terminal window as the one where you set the variables.
Access environment
The login credentials are set in setenv.sh (weblogic:Passw0rd123 ) these will work for all services except Oracle Identity System Administration Console, which use xelsysadm:Passw0rd123.
Service
URL
WebLogic Administration Console
http://kiot.dev.local:7001/console
Oracle Enterprise Manager Console
http://kiot.dev.local:7001/em
Oracle SOA Platform
http://kiot.dev.local:8001/soa-infra
Oracle Identity Self Service Console
http://kiot.dev.local:14000/identity
Oracle Identity System Administration Console
http://kiot.dev.local:14000/sysadmin
WebLogic Administration Console (oimadmin)
Identity Self Service Console (oimms)
Troubleshooting
Container out of memory
If you get an error similar to:
Solve it by configuring ulimits to your container. Either do this globally, or locally, in the docker-compose.yml file. I think it's easiest to do it globally and apply to all containers like so:
Domain Configuration failed
The issue is likely due to password requirements are not being met. Change password in the setenv.sh file to something longer and/or more complex. For dev installations I use Passw0rd123 which suffice.
Stuck at startup
If your SOA or IOM container get stuck at startup and the logs don't get past:
It may be that you don't meet the hardware requirements. I had my last container, OIM, stuck at this stage until I noticed that the RAM was maxed out. Increasing the RAM from 8 to 16 GB solved it and I was able to start all four containers.
kiot :: ~/oracle » docker logs -f oimadmin
... snip ...
sys.argv[19] = -hostname
sys.argv[20] = kiot.localdomain
Error: set() failed. Do dumpStack() to see details.
Error: runCmd() failed. Do dumpStack() to see details.
Traceback (most recent call last):
File "/u01/oracle/dockertools/createOIMDomain.py", line 433, in <module>
provisioner.createOimDomain(domainName, domainUser, domainPassword, rcuDb, rcuSchemaPrefix, rcuSchemaPassword,domainType, hostName)
File "/u01/oracle/dockertools/createOIMDomain.py", line 63, in createOimDomain
domainHome = self.createBaseDomain(name, user, password, domainType)
File "/u01/oracle/dockertools/createOIMDomain.py", line 76, in createBaseDomain
set('Password', password)
File "/tmp/WLSTOfflineIni15508568619490940666.py", line 79, in set
command("set", attrName,value)
File "/tmp/WLSTOfflineIni15508568619490940666.py", line 19, in command
return WLS.runCmd(name, args)
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:3145)
at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:747)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException
Problem invoking WLST - Traceback (most recent call last):
File "/u01/oracle/dockertools/createOIMDomain.py", line 433, in <module>
provisioner.createOimDomain(domainName, domainUser, domainPassword, rcuDb, rcuSchemaPrefix, rcuSchemaPassword,domainType, hostName)
File "/u01/oracle/dockertools/createOIMDomain.py", line 63, in createOimDomain
domainHome = self.createBaseDomain(name, user, password, domainType)
File "/u01/oracle/dockertools/createOIMDomain.py", line 76, in createBaseDomain
set('Password', password)
File "/tmp/WLSTOfflineIni15508568619490940666.py", line 79, in set
command("set", attrName,value)
File "/tmp/WLSTOfflineIni15508568619490940666.py", line 19, in command
return WLS.runCmd(name, args)
at com.oracle.cie.domain.script.jython.CommandExceptionHandler.handleException(CommandExceptionHandler.java:69)
at com.oracle.cie.domain.script.jython.WLScriptContext.handleException(WLScriptContext.java:3145)
at com.oracle.cie.domain.script.jython.WLScriptContext.runCmd(WLScriptContext.java:747)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
com.oracle.cie.domain.script.jython.WLSTException: com.oracle.cie.domain.script.jython.WLSTException
ERROR: Domain Configuration failed. Please check the logs