Avoid to use volume for oracle

[albfan]

If you remove

VOLUME ["/u01/app/oracle"]

from Dockerfile, it will be not mounted by default (empty) so you can have static databases

1. Import a dump
2. save a tag with docker commit
3. Share image tagged for CI, testing, etc...

albfan@3a9a3b5

[MaksymBilenko]

@albfan there was some issues on different platforms. Could you please play around Dockerfile/VOLUME and test it on Windows/Mac/Linux?
Thank you

[MaksymBilenko]

@albfan it makes sense...

[albfan]

Sure, I can report feedback for Windows/Linux

[albfan]

Windows working correctly. I think that's enough to test this.

The only concern is to clearly document how to use existing databases with volume, but README is well documented

[albfan]

Just seen: 4dd6591

[filippetrovic]

But now we can not configure this volume from Kitematic.
Can we make some compromise solution?

[albfan]

Opps! docker/kitematic#1923.

@filippetrovic add a volume because a third party app does not work without it seems wrong. You can always extend this dockerfile to have your volume but that's only a workaround for kitematic (someone needs to implement an add volume)

[filippetrovic]

Same thoughts here.
But I'm not sure what is semantic of VOLUME keyword in Dockerfile.
However, I do not insist on reverting this change.