CODEWITHSUNDEEP
dockeropenshift-origin
Devs love ZenUML
Devs love ZenUML

Reputation: 11842

Is the Openshift Origin Docker image production ready?

I would like to know if it is recommended to use that image in production environment. Or should I install Openshift Natively?

If I can use the docker image in production how should I upgrade it when a new version of image is released? I know I lose all configuration and application definition when starting a new docker container. Is there a way to keep them? Mapping volumes? Which volumes should be mapped?

The command line I am using is: $ sudo docker run -d --name "origin" \ --privileged --pid=host --net=host \ -v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys -v /var/lib/docker:/var/lib/docker:rw \ -v /var/lib/origin/openshift.local.volumes:/var/lib/origin/openshift.local.volumes \ openshift/origin start

PS. There is a relative question I asked yesterday but not focusing on the same problem.

Update on 20/01/2016

I have tried @Clayton's suggestion of mapping folder /var/lib/origin which worked well before 17th Jan 2016. Then I started getting Failed to mount issue when deploying router and some other applications. When I change it back to mapping /var/lib/origin/openshift.local.volumes, it seems OK until now.

Upvotes: 1

Views: 755

Answers (1)

Clayton
Clayton

Reputation: 3316

If you have the /var/lib/origin directory mounted, when your container reboots you will still have all your application data. That would be the recommended way to run in a container.

Upvotes: 2

Related Questions