Closed tberne closed 4 years ago
I ran into the same problem. Not sure what caused it, probably prematurely exiting container. However, it can be fixed in two ways.
Easy:
Deleting the contents of the shared volume from your file system:
rm -r -f /local/comupter/volume/*
A little harder:
Start docker container with
docker run -p 8080:8080 -p 1521:1521 -v /local/comupter/volume/:/container/volumn/ -ti sath89/oracle-12c bash
Repair entrypoint.sh
sed -i "s/mv \(\/u01\/app\/oracle-product\/12.1.0\/xe\/dbs \/u01\/app\/oracle\/dbs\)/cp -r \1/" /entrypoint.sh
Run entrypoint.sh
/entrypoint.sh
Hopefully the owner will make a perminate fix soon: Its in entypoint.sh at line 73
Looks like database corruption due to hard stop.
@jozsefmorrissey Now sure what kind of fix you are looking for. If you have any suggestion you are welcome to create PR with detailed explanation
Looks like database corruption due to hard stop.
Actually, it was the very first time the container has been started. So, I don't believe it is something like database corruption due to hard stop, since there was no stop at all.
Volumes from host might have issues. Try to use docker volumes (non hostPath) like -v oracle12_data:/u01/app/oracle
@MaksymBilenko, I'll try that later and post the results here.
Using docker volumes in my docker-compose.yml
solved this issue.
I could solve the issue with Cannot create directory
and Error writing into silent log -
by chmod -R a+w /home/user1/oracle12-data
This is the directory I used when running the docker
docker run -p 8080:8080 -p 1521:1521 -v /home/user1/oracle12-data:/u01/app/oracle -d sath89/oracle-12c:latest
I could solve the issue with
Cannot create directory
andError writing into silent log -
bychmod -R a+w /home/user1/oracle12-data
This is the directory I used when running the dockerdocker run -p 8080:8080 -p 1521:1521 -v /home/user1/oracle12-data:/u01/app/oracle -d sath89/oracle-12c:latest
i try this,its helpful
Hi. I'm trying to start a container in a Linux box. It fails in both, docker and docker-compose.
Here's my compose configuration:
Here's the container output:
When removing the volume mapping, the container starts well.