Re: containers

I agree with Tim that our use case was definitely at the edge and we had to take a sledgehammer to that square peg to make it work.

We had a few different ways to manage the data files but none of them stored the database with the Docker image. There are myriad storage engines that can be used and orchestration products like Kubernetes add a lot of additional options

Our initial implementation used disks from the host. That's what I showed in the demonstration as well. NFS is another option.

Seth

On Wed, May 29, 2019, 1:20 PM Jeff Chirco <backseatdba_at_gmail.com> wrote:

> Ok I can understand CICD environments but how big were these databases?
> Isn't the database part of the docker image? And did data change from
> production not matter?
>
> On Wed, May 29, 2019 at 8:29 AM Seth Miller <sethmiller.sm_at_gmail.com>
> wrote:
>
>> We use Docker and now Kubernetes extensively in CICD software testing,
>> including in some cases Oracle databases. In a product I worked in
>> previously, we used Docker to spin up dozens of Oracle RAC systems daily.
>> This was a couple of years ago when Oracle told us it was impossible and
>> pointless.
>>
>> Seth
>>
>> On Wed, May 29, 2019 at 2:17 AM Tim Hall <tim_at_oracle-base.com> wrote:
>>
>>> Hi.
>>>
>>> We are using Docker for the application layer mostly. We have out Oracle
>>> REST Data Services (ORDS) running on Tomcat inside Docker. It's awesome and
>>> saves me so much time and is so much more flexible compared to when I was
>>> using regular tomcat instances. I think Docker fits in the middle tier so
>>> well that I now get annoyed when I have to use a regular VM.
>>>
>>> For one project I do web servers (Nginx), app servers (Rails) and
>>> databases (PorsgreSQL) all in Docker, using Swarm to define the
>>> infrastructure. I'm very happy with it. Small footprint database etc. Every
>>> weekend I rebuild all the images and replace the whole infrastructure with
>>> the latest & greatest in a few minutes. The "maintenance window" is a
>>> complete replacement of the entire stack. Docker is awesome for this.
>>> Obviously, config and data is kept in persistent volumes so it isn't lost.
>>>
>>> Typically I wouldn't recommend using Oracle in Docker. It works. I do it
>>> for demos, but really it's a play thing. I can't imagine doing anything
>>> serious with an Oracle database and Docker. Speaking to other folks, I get
>>> the same vibe from them. Large monolithic applications (Oracle, WebLogic
>>> etc.) don't play too well with Docker. They don't follow the typical
>>> container lifecycle of throw it away and replace with a newer version of
>>> the software.
>>>
>>> I've written a bunch of stuff about it here.
>>>
>>> https://oracle-base.com/articles/linux/articles-linux#docker
>>>
>>> I think that pretty much sums up my opinion on it, but it is just my
>>> opinion. :)
>>>
>>> Cheers
>>>
>>> Tim...
>>>
>>>>
>>>>

--
http://www.freelists.org/webpage/oracle-l