Unable to build OracleFusionMiddlewareInfra Image

[arslancse]

Ignoring failure(s) of required prerequisite checks and continuing.
Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2025-01-07_11-29-12AM
Log: /tmp/OraInstall2025-01-07_11-29-12AM/install2025-01-07_11-29-12AM.log
Setting ORACLE_HOME...
SettingINSTALL_TYPE...
Copyright (c) 1996, 2019, Oracle and/or itsaffiliates. All rights reserved.
Reading response file..
Skipping Software Updates
Validations are disabled for this session.
Verifying data
Copying Files
Internal Error: File Copy failed. Aborting Install
Jan 07, 2025 11:29:17 AM oracle.as.install.engine.modules.configuration.ConfigurationModule onExit
INFO: Cleaning up Configuration Module

The log(s) can be found here: /tmp/OraInstall2025-01-07_11-29-12AM.

and by looking at log file it says

Caused by: oracle.sysman.nextgen.NextGenInstallerException: Unable to locate the startup/shiphome directory
at oracle.sysman.nextgen.factory.GdrSessionFactory.getDistributionSession(GdrSessionFactory.java:271)
at oracle.sysman.nextgen.factory.GdrSessionFactory.initInstallerSession(GdrSessionFactory.java:225)
at oracle.sysman.nextgen.factory.GdrSessionFactory.getInstallerSession(GdrSessionFactory.java:167)
at oracle.sysman.nextgen.factory.GdrSessionFactory.getGdrInstallSession(GdrSessionFactory.java:79)
at oracle.sysman.nextgen.wizard.silent.tasks.SilentInstallationValidationTask.execute(SilentInstallationValidationTask.java:96)
... 2 more

[ddsharpe]

@arslancse The recommended method to create container images for WebLogic products is by using WebLogic Image Tool.. Documentation

The docker-images project is maintained as an example of a Dockerfile for building similar images. The WebLogic images that Oracle publishes to Oracle Container Registry are created with WebLogic Image Tool. Both patched and unpatched container images are available on the Oracle Container Registry. But, you can build your own custom images with exactly the patches that you want by using the WebLogic Image Tool.

[arslancse]

You are right but the question is why i am facing that error or issue what ever is. If i want to build my own image by using that dockerfile what is that error exactly mean and how to fix ?

[ddsharpe]

Without looking at more of the log file, I cannot be sure if the Exception message is a result of the file copy error or the explanation of the cause. Keying off of the message Internal Error: File Copy failed. Aborting Install, my first guess is that your build environment ran out of space. Docker/Podman allocate a discrete amount of space for building container images. When that space is no longer big enough to accept new files or copied files, this is the sort of error that occurs. Its not a super friendly error message. Try cleaning up the build environment. You can try things like:

• Remove a couple of unneeded images with docker rmi {image name or id}
• or docker system prune
• or docker volume prune
• ...