I dont have access to following path . Is there any workaround for this ?
Below is output
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
Checking Docker version.
Checking if required packages are present and valid...
LINUX.X64_193000_db_home.zip: OK
==========================
Container runtime info:
Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc., v0.8.2)
compose: Docker Compose (Docker Inc., v2.5.0)
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc., 0.6.0)
scan: Docker Scan (Docker Inc., v0.17.0)
Server:
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 8
Server Version: 20.10.14
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8
runc version: v1.0.3-0-gf46b6ba
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 5.10.16.3-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 24.83GiB
Name: docker-desktop
ID: N4X6:HRH2:UF3Z:GRQK:WMXY:HUY2:AWCS:BOGH:FUHM:EBU5:MG6X:5MJN
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5000
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
==========================
Building image 'oracle/database:19.3.0-ee' ...
#1 [internal] load build definition from Dockerfile
#1 sha256:ae0bf8353f102e2f8f9e35df8915f58f3a04c44b8ecd3bf6b9c4027781247104
#1 transferring dockerfile: 32B done
#1 DONE 0.0s
#2 [internal] load .dockerignore
#2 sha256:86338296bc76941bdd90d929345ead3ac30c6af3e937e2b34964e86e4e6275c7
#2 transferring context: 2B done
#2 DONE 0.0s
#3 [internal] load metadata for docker.io/library/oraclelinux:7-slim
#3 sha256:87ecd7bcbbc3ba1f1518cb46893e8d1a9cd73f72ecadc1fda045f513522c16a6
#3 DONE 33.3s
#4 [base 1/5] FROM docker.io/library/oraclelinux:7-slim@sha256:ce16f06496bdc911eeba5cd9bc38372da0d8b758638dfb1502ff0aa1704b590e
#4 sha256:8fa62a74be78d790668f66691a9b754511843b389b9016de225159b7027e53f0
#4 CACHED
#6 [internal] load build context
#6 sha256:1f49e2ec4d93bf224a3eead04c5a8d6be8c2a3d984f0fdecb0106335930cb954
#6 transferring context: 504B done
#6 DONE 0.0s
#5 [base 2/5] RUN echo "sslverify=false" >> /etc/yum.conf
#5 sha256:26c4d411b9f1c35e526fc7456a2d139f9727972e7e45a3e901425b5794e23ee3
#5 DONE 0.4s
#7 [base 3/5] COPY setupLinuxEnv.sh checkSpace.sh /opt/install/
#7 sha256:73ac30c8c3eeb06fdbc693e04b366dd67adfb212df26a9cb6be44fac60932f0c
#7 DONE 0.0s
#8 [base 4/5] COPY runOracle.sh startDB.sh createDB.sh createObserver.sh dbca.rsp.tmpl setPassword.sh checkDBStatus.sh runUserScripts.sh relinkOracleBinary.sh /opt/oracle/
#8 sha256:90b395f8fe8e56cbc9143ba6f5bcb010c23767866db222692292b07a086bdca8
#8 DONE 0.1s
#9 [base 5/5] RUN chmod ug+x /opt/install/*.sh && sync && /opt/install/checkSpace.sh && /opt/install/setupLinuxEnv.sh && rm -rf /opt/install
#9 sha256:2e350b78369e78ba0aa4fb6677b533e12305158763dabc8b3c055b5bc94850c4
#9 0.605 Loaded plugins: ovl
#9 2.928 https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/repodata/ab949214e7975e1774d0b9b84e915f974bf0a135-primary.sqlite.bz2: [Errno 14] HTTPS Error 403 - Forbidden
#9 2.928 Trying other mirror.
#9 4.373 https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/repodata/ab949214e7975e1774d0b9b84e915f974bf0a135-primary.sqlite.bz2: [Errno 14] HTTPS Error 403 - Forbidden
#9 4.373 Trying other mirror.
#9 5.587 https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/repodata/ab949214e7975e1774d0b9b84e915f974bf0a135-primary.sqlite.bz2: [Errno 14] HTTPS Error 403 - Forbidden
#9 5.587 Trying other mirror.
#9 5.588
#9 5.588
#9 5.588 One of the configured repositories failed (Oracle Linux 7Server Latest (x86_64)),
#9 5.588 and yum doesn't have enough cached data to continue. At this point the only
#9 5.588 safe thing yum can do is fail. There are a few ways to work "fix" this:
#9 5.588
#9 5.588 1. Contact the upstream for the repository and get them to fix the problem.
#9 5.588
#9 5.588 2. Reconfigure the baseurl/etc. for the repository, to point to a working
#9 5.588 upstream. This is most often useful if you are using a newer
#9 5.588 distribution release than is supported by the repository (and the
#9 5.588 packages for the previous distribution release still work).
#9 5.588
#9 5.588 3. Run the command with the repository temporarily disabled
#9 5.588 yum --disablerepo=ol7_latest ...
#9 5.588
#9 5.588 4. Disable the repository permanently, so yum won't use it by default. Yum
#9 5.588 will then just ignore the repository until you permanently enable it
#9 5.588 again or use --enablerepo for temporary usage:
#9 5.588
#9 5.588 yum-config-manager --disable ol7_latest
#9 5.588 or
#9 5.588 subscription-manager repos --disable=ol7_latest
#9 5.588
#9 5.588 5. Configure the failing repository to be skipped, if it is unavailable.
#9 5.588 Note that yum will try to contact the repo. when it runs most commands,
#9 5.588 so will have to try and fail each time (and thus. yum will be be much
#9 5.588 slower). If it is a very temporary problem though, this is often a nice
#9 5.588 compromise:
#9 5.588
#9 5.588 yum-config-manager --save --setopt=ol7_latest.skip_if_unavailable=true
#9 5.588
#9 5.588 failure: repodata/ab949214e7975e1774d0b9b84e915f974bf0a135-primary.sqlite.bz2 from ol7_latest: [Errno 256] No more mirrors to try.
#9 5.588 https://yum.oracle.com/repo/OracleLinux/OL7/latest/x86_64/repodata/ab949214e7975e1774d0b9b84e915f974bf0a135-primary.sqlite.bz2: [Errno 14] HTTPS Error 403 - Forbidden
#9 ERROR: executor failed running [/bin/sh -c chmod ug+x $INSTALL_DIR/*.sh && sync && $INSTALL_DIR/$CHECK_SPACE_FILE && $INSTALL_DIR/$SETUP_LINUX_FILE && rm -rf $INSTALL_DIR]: exit code: 1
------
> [base 5/5] RUN chmod ug+x /opt/install/*.sh && sync && /opt/install/checkSpace.sh && /opt/install/setupLinuxEnv.sh && rm -rf /opt/install:
------
executor failed running [/bin/sh -c chmod ug+x $INSTALL_DIR/*.sh && sync && $INSTALL_DIR/$CHECK_SPACE_FILE && $INSTALL_DIR/$SETUP_LINUX_FILE && rm -rf $INSTALL_DIR]: exit code: 1
ERROR: Oracle Database container image was NOT successfully created.
ERROR: Check the output and correct any reported problems with the build operation.
You should consult the system administrators of the company why it works if you try to the “repodata” page first. They can check the firewall logs. I had similar issues where I work too.
As for the SSL issue, it may be related to why the firewall blocks the request, I just don’t know the reason.
You can try at least one thing. install “ca-certificates” in the image, but I would be surprised if Oracle hadn’t thought of it.
I also wanted to recommend that you have already done. And this is creating an issue on GitHub:
Hello @rimelek regarding installing ca-certificates . I have never done this before . Is there any link which helps in explaining this. I am trying to find it out but what I am not getting is where do I need to run this in docker file.
also do I need to run these as YUM commands . This is new to me . Never done this before.
Have you followed @rimelek’s advise and asked your system admistrators? Your problems are caused of some security or complience mechanisms your company applies - they should be able to tell you what the problem is, while we can guess at best.