-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error Building OracleFormsReports #1
Comments
Hi @Holodny , you are right, you have to disable SELinux on your Docker host. I will update the README.md. Cheers |
I disabled Selinux on the host and rebooted and checked the sestatus and it showed disabled. I ran again as regular user and root and still get this error: Step 13/16 : RUN cd /opt && ./$FMW_BIN -silent -responseFile /opt/formsreports.response -invPtrLoc /opt/oraInst.loc -jreLoc $JAVA_HOME -ignoreSysPrereqs -force -novalidation ORACLE_HOME=$ORACLE_HOME && rm -fr /opt/.bin /opt/.zip /opt/.response /opt/.loc I looked for the installer logs in the /tmp directory and they weren't there. I'm not sure if the messages referring to log files are referring to the host machine tmp directory or a tmp directory in the container? I tried running the container and adding an entry point to see if the error log was in the container but haven't been successful yet. |
Hi @Holodny , the tmp directory in your case is inside the Image, not mapped. You should check, if you have set the parameter Another point which you should check is, if your Docker host have enough free disk space, specially the mapped volume (in case this is an extra disk). Cheers |
Hi @Holodny |
Hi Dirk, I was able to build everything involved in the 12.2.1.3 section until I got to the OracleFormsReports. I ran them and ran into the error shown in the image below. You'll notice I'm running as root this time, I tried it as the normal user previously and got the same error.
I'm running the build on a Centos 7 virtual machine on VirtualBox. I think it's having issues with writing to the /tmp folder, maybe because of Selinux? I think this because of the failure and because when I go to look for the log that it says is under the /tmp directory, it's not there.
The text was updated successfully, but these errors were encountered: