Open artnaseef opened 6 years ago
+1 for this. I believe this is taking a while because every time the container starts up it attempts to install Oracle DB from scratch. Infact, if you had to restart the container after the installation finishes, it would take much less time to become available again.
I suggest you to run container, init database and then commit it and use for your purposes.
Is there really no way to speed up the database initialization otherwise?
It looks like the resulting image will be huge (multiple gigabytes). I'll try committing an image and verify the size.
Committing after the DB builds, the image is 8.39GB
Isn't that a really too large?
I would love to know if there's a way to shrink this size too, but I have a feeling given that the oracle binary downloads for 12c are almost 4gb by themselves, there may not be much hope...
I'm using this image for build-time integration tests. In that role, the 10 minute startup time that we experience is high.
Any thoughts on how we could reduce this startup time? I tried a few things a while back (don't recall the exact settings now), but none of them helped.
To clarify, the "tnslsnr" startup is the vast majority of the startup time taken.