-
Notifications
You must be signed in to change notification settings - Fork 6
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
Loads of permission issues when trying to start the image #7
Comments
Try using absolute paths for the volumes. |
same issue i'm afraid. I changed the manageOracle.sh script where the ls -l /u03/app/
ls -l ${RECO}
mkdir -p "${RECO}/fast_recovery_area/${ORACLE_SID}" || error "Could not create the FRA directory for ${ORACLE_SID}" And when that part of the script is executed, this is the output:
|
That error is saying that the path in the container can't be created. Since it's referencing a volume on the host, it needs (first) an absolute path (container ecosystems don't do relative paths) and correct permissions on the local volume.
Change the local path used for mounting the volumes to something like:
|
rookie error on my part. I had the trailing slash in my compose file (look at the volumes) because i copied/pasted your docker command in the readme and pasted it to my compose file but forgot to remove them. Now im trying to get the image to run my scripts to populate the database like this one. Sorry for wasting your time |
Hello,
I followed the documentation and was able to build 19.19 on my macbook, but I can't get it to start regardless whether i use compose or not
compose:
All of the directories are empty and even have 777 pernissions. Startup logs:
Any help would be greatly appreciated, and happy to help test to get it working.
The text was updated successfully, but these errors were encountered: