-
Notifications
You must be signed in to change notification settings - Fork 799
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
Persisting Data with Volumes #119
Comments
Bit more information Whenever I try to use --mount, when I exec into the container I can't access the database, constantly says it's shutting down or starting up ORA-01033: ORACLE initialization or shutdown in progress Here's the alert log Enter user-name: root@d1956113a860:/# cat Whenever I try to use the -v option, it will work first time, so I import some data, stop and remove the container, run it again mapping to the volume, and then I see similar errors, and the database always either shutting down or starting up making it unusable. |
I've now tried this within a docker-compose context
docker-compose up works beautifully, and I docker exec into the container, and import some data with imp. Then I run docker-compose down, and docker-compose up again, and this error pops up in the output from the compose command
|
I've run into the same problem - adding a mounted volume over the oradata directory works first time but then after a restart Oracle won't start properly - any ideas @wnameless ? |
Hi everyone i found a fix for this problem. |
It works for me as well. Thanks!! |
1 similar comment
It works for me as well. Thanks!! |
how did you get this to work exactly? Im struggling. would rather data not stored in the container. |
Hi, This is the command I wrote: docker run -d -p 1521:1521 -e ORACLE_ALLOW_REMOTE=true -v oracle:/u01/app/oracle wnameless/oracle-xe-11g-r2 |
Hi, is there anyone fix this issue? I'd just like to share a work around using k8s environment:
okay, now will be the tricky part:
I know this is not a proper way to solve this issue, just a work around as I mentioned. I really keen to hear a final solution from you guys! |
HI Everyone
I'm on mac, docker versions are
Server: Docker Engine - Community
Engine:
Version: 18.09.2
Client: Docker Engine - Community
Version: 18.09.2
I've tried what seems to be every conceivable way of persisting data, using -v, or --mount, but nothing seems to be working. I think I must be getting the path to where the data exists inside the container wrong or something.
Is persisting data possible with my versions above and this image? I've got a saved image prior to the image being pulled from docker hub, which was very sad btw, not your fault I know. :-(
Thanks for any tips or suggestions.
The text was updated successfully, but these errors were encountered: