Hi guys,
yes mounting /var/lib/origin works, and also, you can use the
create-config flags to use it in a more configurable way.
But, the main limitation that I see is around SDN, which I think cannot
be used as-is.
Can someone confirm?
Le 12/01/16 03:51, Clayton Coleman a écrit :
Hi, tried to answer on stack. You should be able to mount the
/var/lib/origin directory and have everything preserved (but double
check the default directories created).
On Mon, Jan 11, 2016 at 8:20 PM, Xiao Peng <[email protected]> wrote:
Hi all,
I am relatively new to Openshift Origin. We are designing a solution for
service integration and want to use Openshift Origin as the platform. But I
wonder if I should use the docker image 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:
docker run -d --name "origin" -e "http_proxy=$http_proxy" -e
"https_proxy=$https_proxy" -e "no_proxy=$no_proxy" --privileged --pid=host
--net=host -v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys
openshift/origin start --cors-allowed-origins='.*'
I have also asked this question on stackoverflow (
http://stackoverflow.com/questions/34734062/is-the-openshift-origin-docker-image-production-ready
).
Thanks,
Xiao Peng, Technical Architect
Blog: http://mrcoder.github.io/
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
_______________________________________________
dev mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
