Oracle Fusion Middleware Infrastructure 12.2.1.3

Docker Hub
1

Hi,

I am trying to run " Oracle Fusion Middleware Infrastructure 12.2.1.3 ", based on:
“hub.docker.com”

The DB starts and is healthy, I have created the properties files and defined the environment variables, but when I try to create a new container, with the following command:

$ docker run
-d
-p 9001:7001
-p 9002:9002
–name InfraAdminContainer
–net=InfraNET
-v /home/oss/properties:/u01/oracle/properties
-v /home/oss/domain_host_volume:/u01/oracle/user_projects/domains
-e DOMAIN_NAME=myinfraDomain
-e ADMIN_NAME=myadmin
-e ADMIN_HOST=InfraAdminContainer
-e ADMIN_LISTEN_PORT=7001
-e MANAGEDSERVER_PORT=8001
-e MANAGED_NAME=infraServer1
-e ADMINISTRATION_PORT_ENABLED=true
-e ADMINISTRATION_PORT=9002
-e RCUPREFIX=INFRA01
-e PRODUCTION_MODE=dev
-e CONNECTION_STRING=InfraDB:1521/InfraPDB1.us.oracle.com
store/oracle/fmw-infrastructure:12.2.1.3

… there is an error: “docker: Error response from daemon: unable to find user oracle: no matching entries in passwd file.”.

I have careful read how the image has been built, in “https://github.com/oracle/docker-images/commit/4ed434bdc061a5491270aa1173bf1139aadef274”, and I couldn’t find the issue.

When I try to read the container logs, there also an error: “Error response from daemon: readlink /var/lib/docker/overlay2/l: invalid argument”. This means I cannot see what happens when the container is being created.

I installed Docker 19.03.2 in Linux 7.6, in a Virtual Box image, in my laptop extracting “docker-19.03.2.tgz”.

Could anybody help? Is the problem with my Docker installation? or with the Image? or with the properties/variables?

Many thanks.
Regards,
David G.

2

The Docker startup logs are:

[oss@myvirtualserver ~] sudo cp docker/* /usr/bin/* *[oss@myvirtualserver ~] sudo dockerd &
[oss@myvirtualserver ~]$ INFO[2019-10-11T16:35:51.969309550+02:00] Starting up
INFO[2019-10-11T16:35:51.971713736+02:00] libcontainerd: started new containerd process pid=4577
INFO[2019-10-11T16:35:51.971761286+02:00] parsed scheme: “unix” module=grpc
INFO[2019-10-11T16:35:51.971772966+02:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2019-10-11T16:35:51.972100857+02:00] ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock 0 }] } module=grpc
INFO[2019-10-11T16:35:51.972125099+02:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2019-10-11T16:35:51.972198026+02:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000708270, CONNECTING module=grpc
INFO[2019-10-11T16:35:51.990719491+02:00] starting containerd revision=894b81a4b802e4eb2a91d1ce216b8817763c29fb version=v1.2.6
INFO[2019-10-11T16:35:51.991435821+02:00] loading plugin “io.containerd.content.v1.content”… type=io.containerd.content.v1
INFO[2019-10-11T16:35:51.991528344+02:00] loading plugin “io.containerd.snapshotter.v1.btrfs”… type=io.containerd.snapshotter.v1
WARN[2019-10-11T16:35:51.992444770+02:00] failed to load plugin io.containerd.snapshotter.v1.btrfs error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter”
INFO[2019-10-11T16:35:51.992474174+02:00] loading plugin “io.containerd.snapshotter.v1.aufs”… type=io.containerd.snapshotter.v1
WARN[2019-10-11T16:35:52.006214394+02:00] failed to load plugin io.containerd.snapshotter.v1.aufs error=“modprobe aufs failed: “modprobe: FATAL: Module aufs not found.\n”: exit status 1”
INFO[2019-10-11T16:35:52.006249949+02:00] loading plugin “io.containerd.snapshotter.v1.native”… type=io.containerd.snapshotter.v1
INFO[2019-10-11T16:35:52.006314772+02:00] loading plugin “io.containerd.snapshotter.v1.overlayfs”… type=io.containerd.snapshotter.v1
INFO[2019-10-11T16:35:52.006406238+02:00] loading plugin “io.containerd.snapshotter.v1.zfs”… type=io.containerd.snapshotter.v1
WARN[2019-10-11T16:35:52.006768971+02:00] failed to load plugin io.containerd.snapshotter.v1.zfs error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter”
INFO[2019-10-11T16:35:52.006792975+02:00] loading plugin “io.containerd.metadata.v1.bolt”… type=io.containerd.metadata.v1
WARN[2019-10-11T16:35:52.006832523+02:00] could not use snapshotter btrfs in metadata plugin error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.btrfs must be a btrfs filesystem to be used with the btrfs snapshotter”
WARN[2019-10-11T16:35:52.006846548+02:00] could not use snapshotter aufs in metadata plugin error=“modprobe aufs failed: “modprobe: FATAL: Module aufs not found.\n”: exit status 1”
WARN[2019-10-11T16:35:52.006860180+02:00] could not use snapshotter zfs in metadata plugin error=“path /var/lib/docker/containerd/daemon/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter”
INFO[2019-10-11T16:35:52.011213248+02:00] loading plugin “io.containerd.differ.v1.walking”… type=io.containerd.differ.v1
INFO[2019-10-11T16:35:52.011261292+02:00] loading plugin “io.containerd.gc.v1.scheduler”… type=io.containerd.gc.v1
INFO[2019-10-11T16:35:52.011403370+02:00] loading plugin “io.containerd.service.v1.containers-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011431221+02:00] loading plugin “io.containerd.service.v1.content-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011452955+02:00] loading plugin “io.containerd.service.v1.diff-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011474477+02:00] loading plugin “io.containerd.service.v1.images-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011502197+02:00] loading plugin “io.containerd.service.v1.leases-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011530733+02:00] loading plugin “io.containerd.service.v1.namespaces-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011571785+02:00] loading plugin “io.containerd.service.v1.snapshots-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.011601549+02:00] loading plugin “io.containerd.runtime.v1.linux”… type=io.containerd.runtime.v1
INFO[2019-10-11T16:35:52.011737151+02:00] loading plugin “io.containerd.runtime.v2.task”… type=io.containerd.runtime.v2
INFO[2019-10-11T16:35:52.011800124+02:00] loading plugin “io.containerd.monitor.v1.cgroups”… type=io.containerd.monitor.v1
INFO[2019-10-11T16:35:52.012327679+02:00] loading plugin “io.containerd.service.v1.tasks-service”… type=io.containerd.service.v1
INFO[2019-10-11T16:35:52.012371863+02:00] loading plugin “io.containerd.internal.v1.restart”… type=io.containerd.internal.v1
INFO[2019-10-11T16:35:52.012423675+02:00] loading plugin “io.containerd.grpc.v1.containers”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012442458+02:00] loading plugin “io.containerd.grpc.v1.content”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012460779+02:00] loading plugin “io.containerd.grpc.v1.diff”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012476675+02:00] loading plugin “io.containerd.grpc.v1.events”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012490785+02:00] loading plugin “io.containerd.grpc.v1.healthcheck”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012507809+02:00] loading plugin “io.containerd.grpc.v1.images”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012522132+02:00] loading plugin “io.containerd.grpc.v1.leases”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012537750+02:00] loading plugin “io.containerd.grpc.v1.namespaces”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012552071+02:00] loading plugin “io.containerd.internal.v1.opt”… type=io.containerd.internal.v1
INFO[2019-10-11T16:35:52.012629141+02:00] loading plugin “io.containerd.grpc.v1.snapshots”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012649094+02:00] loading plugin “io.containerd.grpc.v1.tasks”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012664366+02:00] loading plugin “io.containerd.grpc.v1.version”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012679074+02:00] loading plugin “io.containerd.grpc.v1.introspection”… type=io.containerd.grpc.v1
INFO[2019-10-11T16:35:52.012898325+02:00] serving… address="/var/run/docker/containerd/containerd-debug.sock"
INFO[2019-10-11T16:35:52.012941871+02:00] serving… address="/var/run/docker/containerd/containerd.sock"
INFO[2019-10-11T16:35:52.012954201+02:00] containerd successfully booted in 0.023766s
INFO[2019-10-11T16:35:52.017258501+02:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000708270, READY module=grpc
INFO[2019-10-11T16:35:52.023176456+02:00] parsed scheme: “unix” module=grpc
INFO[2019-10-11T16:35:52.023200458+02:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2019-10-11T16:35:52.023216488+02:00] ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock 0 }] } module=grpc
INFO[2019-10-11T16:35:52.023224758+02:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2019-10-11T16:35:52.023272154+02:00] pickfirstBalancer: HandleSubConnStateChange: 0xc0007089d0, CONNECTING module=grpc
INFO[2019-10-11T16:35:52.023852155+02:00] pickfirstBalancer: HandleSubConnStateChange: 0xc0007089d0, READY module=grpc
INFO[2019-10-11T16:35:52.026149174+02:00] parsed scheme: “unix” module=grpc
INFO[2019-10-11T16:35:52.026177229+02:00] scheme “unix” not registered, fallback to default scheme module=grpc
INFO[2019-10-11T16:35:52.026199456+02:00] ccResolverWrapper: sending update to cc: {[{unix:///var/run/docker/containerd/containerd.sock 0 }] } module=grpc
INFO[2019-10-11T16:35:52.026212003+02:00] ClientConn switching balancer to “pick_first” module=grpc
INFO[2019-10-11T16:35:52.026276675+02:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000709060, CONNECTING module=grpc
INFO[2019-10-11T16:35:52.026680570+02:00] pickfirstBalancer: HandleSubConnStateChange: 0xc000709060, READY module=grpc
INFO[2019-10-11T16:35:52.051302637+02:00] [graphdriver] using prior storage driver: overlay2
INFO[2019-10-11T16:35:52.094542856+02:00] Loading containers: start.
INFO[2019-10-11T16:35:52.387785596+02:00] Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address
INFO[2019-10-11T16:35:52.432571038+02:00] Loading containers: done.
WARN[2019-10-11T16:35:52.450911258+02:00] Not using native diff for overlay2, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled storage-driver=overlay2
INFO[2019-10-11T16:35:52.451152839+02:00] Docker daemon commit=6a30dfca03 graphdriver(s)=overlay2 version=19.03.2
INFO[2019-10-11T16:35:52.451210163+02:00] Daemon has completed initialization
INFO[2019-10-11T16:35:52.472384430+02:00] API listen on /var/run/docker.sock

3

Solved. I think Docker was not properly installed.

4

There are a few steps you must take to prepare for an Oracle Fusion Middleware Infrastructure installation.
Review this section thoroughly to ensure that you don’t encounter any problems during or after product installation and domain configuration.

Using This Document
There are certain scenarios that you want to use this guide for, and other sources of information.
About the Infrastructure Standard Installation Topology
The standard installation topology for Oracle Fusion Middleware Infrastructure has a standard WebLogic Server domain that contains an Administration Server and a cluster containing two Managed Servers.
Roadmap for Installing and Configuring the Standard Installation Topology
There are a series of steps to install and configure a standard Oracle Fusion Middleware Infrastructure installation topology.
Roadmap for Verifying Your System Environment
This topic has important information that you must read and understand before you begin installation and configuration steps.
Obtaining the Infrastructure Distribution
Before you obtain product distributions and run installers, verify that you have a certified JDK installed on your system.
About Installing Oracle User Messaging Service (UMS)
Oracle User Messaging Service (UMS) enables two-way communication between users and applications. UMS is part of the Oracle Fusion Middleware Infrastructure distribution and installs as part of the Oracle Fusion Middleware Infrastructure standard installation topology.
Using This Document
There are certain scenarios that you want to use this guide for, and other sources of information.

This section contains the following topics:

Using the Standard Installation Topology as a Starting Point
This guide helps you create the standard installation topology for Oracle Fusion Middleware Infrastructure. You can extend this topology to make it highly available and secure so that it is suitable for a production system.
Using this Document to Extend an Existing Domain
Procedures in this guide describe how to create a new domain; you can use the same instructions to extend an existing domain.
Using this Document in an Upgrade Scenario
If you are installing Oracle Fusion Middleware Infrastructure as part of an upgrade procedure, follow steps in this guide to install the software, but don’t run the Configuration Wizard to create a WebLogic domain. Learn Oracle Online Training
About Installing a Development Environment
This guide describes how to use the Oracle Fusion Middleware Infrastructure distribution to install and configure a standard installation topology as a starting point for a production environment.

5

Hi,

I have FMW Infractructure 12.2.1.3 running in a Docker Container. I would like to know what password is assigned to the “INFRA01_MDS” DB user. It is not configured as an input parameter.

Thanks.
David G.

6

Hi,

Based on “createOrStartInfraDomain.sh”, the MDS password should be the one configured in “domain_security.properties” (applicable to “sys” too), this mean: “Oradoc_db1”. However this password is not valid, is the latest valued hard-coded?

Refer to the code:

SEC_PROPERTIES_FILE=/u01/oracle/properties/domain_security.properties
…
DB_SCHEMA_PASS=awk '{print $1}' $SEC_PROPERTIES_FILE | grep db_schema | cut -d "=" -f2
…
#Set the password for RCU
echo -e {DB_PASS}"\n"{DB_SCHEMA_PASS} > /u01/oracle/pwd.txt

Thanks.
David G.

7

Solved.

In the “domain_security.properties” file, the RCU schema passwords are the value of the “db_schema” variable.

David G.

8

Hi, is there any way to install new packages by using “yum install”?

The idea is to run this already created image to deploy applications in WLS. Basic commands are missing, like “unzip”.

Thanks
David G.

9

Solved!

Regards,
David G.