I really dont see Docker as stable, and perhaps neither should you.
-
@bigbear docker containers Are for scaleout stateless layers. Lxd/libvirtlxc is like vm but with less overhead. Still you have to check if that overhead really matters.
-
I did a container talk at MangoCon two days ago
Docker is very different than traditional containers that we have had for 35 years. Solaris has been 100% containerized since 2005!
-
@emad-r said in I really dont see Docker as stable, and perhaps neither should you.:
hat surprised me is that sometimes containers needs restart every now and then, especially frequently used ones.
I haven't played a lot with it, but what was the reason for the restarts?
-
I have it hosted an enterprise grade server or Lenovo m5 x3650 in a VM, but after while performance suffers alot. The restarts that I need it to perform to containers was not on daily basis to be honest, but like it occurred a couple of times. But that tarnished my image of Docker, considering how reliable and strong the LAMP stack in any version of Linux.
-
You'll not really benefit from containerized workloads unless you are deploying applications that are designed to be ephemeral and stateless. Trying to deploy an application using a container the same way you deploy an application to a virtual machine, is not the way containers were intended to be used.
Containers should not be thought about in relation to virtual machines, they are two different things. Containers provide an encapsulation and abstraction of a service from the operating system. Containers are not a miniature virtual machine that you deploy your software on or to.
Check out the 12-factor App Methodology for a better explanation:
-
@ramblingbiped said in I really dont see Docker as stable, and perhaps neither should you.:
You'll not really benefit from containerized workloads unless you are deploying applications that are designed to be ephemeral and stateless. Trying to deploy an application using a container the same way you deploy an application to a virtual machine, is not the way containers were intended to be used.
Containers should not be thought about in relation to virtual machines, they are two different things. Containers provide an encapsulation and abstraction of a service from the operating system. Containers are not a miniature virtual machine that you deploy your software on or to.
Check out the 12-factor App Methodology for a better explanation:
Well part of the issue here is that you are describing docker not containers. Docker is a special case as highlighted in my talk.
-
@RamblingBiped thanks for the link
@scottalanmiller its funny you mention Solaris because that is mostly what I think of when I see containers mentioned. Will that talk be online down the road that you gave?
-
@bigbear said in I really dont see Docker as stable, and perhaps neither should you.:
@RamblingBiped thanks for the link
@scottalanmiller its funny you mention Solaris because that is mostly what I think of when I see containers mentioned. Will that talk be online down the road that you gave?
Hopefully the recording comes out. We've not been able to view them yet.
-
Solaris was my first containers too. I always think of Zones first.
-
Please mention another reason for not using Docker with Linux based operating systems:
If the UID on your host system doesn’t match the UID of the user inside your Docker container, you will have file ownership issues.I think most people don’t encounter this because they are probably the only user on their development machine, and most people only add a single user in their Dockerfile to run their app.
I’m not sure about other Linuxes, but Ubuntu will assign the first user a UID of 1000 so if you’re the first user on an Ubuntu host and you have an Ubuntu-based Docker image, you won’t even notice.
Personally, i was given advice to avoid host volumes even though the case can be resolved with bindfs and a privileged machine in a Windows environment.
