Cannot mount previous volume in new container

General Discussions
1

Hi all,
I pulled oracle store/oracle/database-enterprise:12.2.0.1 image and created a container.
I filled this container with data (so volumes are changed…).
I found volumes id and
docker inspect 6d42891616de63ba96011008f2b3c5cfa96209112f831486794e3c339bd910ec

return :

[
{
    "CreatedAt": "2018-10-01T20:03:57Z",
    "Driver": "local",
    "Labels": null,
    "Mountpoint": "/var/lib/docker/volumes/6d42891616de63ba96011008f2b3c5cfa96209112f831486794e3c339bd910ec/_data",
    "Name": "6d42891616de63ba96011008f2b3c5cfa96209112f831486794e3c339bd910ec",
    "Options": null,
    "Scope": "local"
}

]

Now I want to create a new container using previous volume with :

docker run -d --name NEW_CONTAINER -v 6d42891616de63ba96011008f2b3c5cfa96209112f831486794e3c339bd910ec:/var/lib/docker/volumes/6d42891616de63ba96011008f2b3c5cfa96209112f831486794e3c339bd910ec/_data  IMAGE_NAME

but i got:

Start up Oracle Database
Mon Oct 8 12:25:11 UTC 2018
start database
start listener
The database is ready for use .
tail: cannot open '/u01/app/oracle/diag/rdbms/orclcdb/ORCLCDB/trace/alert_ORCLCDB.log' for reading: 
No such file or directory
tail: no files remaining
2

I’m having the same issue. Please let me know if you find something.

3

I am also seeing this same issue. Did anyone figure this out?

4

use -v volume-id:/ORCL

e.g.

docker run -d --name NEW_CONTAINER -v 6d42891616de63ba96011008f2b3c5cfa96209112f831486794e3c339bd910ec:/ORCL IMAGE_NAME