Separate names with a comma.
Discussion in 'Proxmox VE: Installation and configuration' started by aik.fiend, May 19, 2016.
Actually, Docker is not Standard. RunC is the industry standard.
Hi to all !
however the discussion runs:
it would by nice to start a docker container means the application based of this contailer without any additional work and knowledge for USERS like me.
Best regards from Germany
Isn't there integration in WS2016 and VMware? Recently, we got our first customer asking about setting up a docker environment and he is not a developer and we not an infrastructure provider.
Isolated cases determines the industry?
Let's wait for the massive Docker use outside the developer environment...
If you believe in the cloud providers, there are millions of containers out there. Obviously, not all on docker, but similar techniques. Biggest are AWS and nowadays also Azure. Maybe the goals of Proxmox VE and a real PaaS-Cloud with Docker are just too different, maybe even disjoint.
I assume you know that (almost) everything at Google runs in containers, right?
Oh yeah ... I forgot Google and their kubernetes stuff. The industry in currently in a big change towards continuous deployment, so there is no need for "old" virtualization techniques besides providing the infrastructure. That is going to be a big game changer for the administrators, because they do not need to prepare machines etc, the developers can just deploy them and everything works. It's really amazing how simple that is at the moment.
I read through that awhile back and it gave me the impression that running docker in an LXC would be mildly difficult and occasionally buggy. The thread is nearly two years old at this point. Has anyone tried running Docker in an LXC on Proxmox 4.4? I have an app I need to deploy which is being published as a Docker image.
Just picking up...As said before, Docker stuff would be great, but it will take lots of time to develop and test which i think is better spent on other tasks. It's not VMware having huge amount of developers, also the PVE team does a great job not only providing a hypervisor, just think of all the storage possibilities. Would be great if there are resources, but can live without.
Last week i've got some spare time to check if and how we can use some "cloud service" internally. Ended up using each platform for what it does best. Proxmox for KVMs, which are part of a Docker Swarm. Setting up using ansible and my "kickseed" stuff with some services (Selenium Grid, CI Runners, ...) took my a day, finalizing another one, documentation and creating a workshop for our developers probably whole next week
Things i've used:
- Proxmox of course!
- https://docs.ansible.com/ansible/proxmox_kvm_module.html + Preseed to create Swarm Nodes
- Docker Swarm
Thank's for sharing. I'm also currently investigating docker swarm on Proxmox VE and your list will help a lot!
The whole setup was blazing fast with our CI tests, devs are loving me right now No problem there with stateless containers, in fact this is desirable to have a clean state on each CI run.
For production services, i'm trying the same just backed with some persistent storage. Guess it will be Ceph, as it's already builtin
Thinking of self-healing production services makes me smile...
Added another fancy thing to the Swarm: http://proxy.dockerflow.com/
ah that portainer is pretty epic!
thanks for that gui
I also investigated docker-machine and played around a little with their drivers. Maybe there is someone willing to create a Go driver for Proxmox VE such that you can use the Proxmox VE IaaS to deploy docker fully-automatic with docker-machine. A simple working example should not be too hard if you're familiar with Go. I tried, but I do not have time right now to learn go and get it to work. I played around with the proxmox-go library and got simple authentication working. If someone would be interested in programming it, I can talk you through - just contact me.
That would IMHO be the best way to deploy Docker (PaaS) on Proxmox VE (IaaS) - use each technology for what they were created.
I have been experimenting with nomad+consul to create VMs which are able to create dockers.
A two tier architecture;
* one set of nomad+consul monitors the VMs ("qm agent NNN network-get-interfaces" as a health check to mark machine is ONLINE)
* second set of nomad+consul for the dockers created inside each VM (as per requirement)
these dockers which may scale out/scale in can be reached from outside using a proxy like "gobetween" or "haproxy+consul-template"
This is in a very (very very) basic form and the setup itself is not automated.
I may have more when I am able to "automize" the end-to-end flow for setting up a new PVE server to creating VMs as well.
finally after checking docker out for a while I see the big benefit.
But running docker with a ceph backend, is there already a working solution?
I found https://clusterhq.com/flocker/introduction/ and saw that docker took flocker over.
Don't think they have released something that integrated it yet?
Right now, there's a huge gap (and need) for elastic persistent storage. Here's a list of current available volume plugins:
However it is not up to date yet. I don't like the idea of block storage attached to containers, as it's mor work to extend/shrink compared to file systems. My lab system right now is running GlusterFS (withoug plugin unfortunately, just mounts on all swarm nodes). Currently, Minio is a rising star, easy to use, easy to scale, cluster/cloud in mind. As it's S3 and defacto standard, i would love if storage becomes more application centric instead of infrastructure read have the app talking to S3 directly instead of letting the OS take care of.
a relatively straightforward way to implement docker support would be to use clear containers.
These already use KVM to provide docker containers in a virtualized environment and also support management with kubernetes.
In the next month or so I'll try setting this up on a proxmox base.
What for? Clear container already use qemu, so why don't you use a simply VM instead?
clear containers have a few dvantages, as far as I can see,
they are faster to boot as the vm is stripped down
they support virtFS
they have an inbuild management interface that can talk to kubernetes
For deployment purposes, tjis allows spinning up and down docker instances in a managed fashion. It also allows load balancing and network autodiscovery which is hard to achieve with a standard vm.