Is Docker a joke or do I just not see the point?
-
@stacksofplates said in Is Docker a joke or do I just not see the point?:
But they might not be, they might be constant, never go down cases and would then require updates just like any other system.
This is weird and not the use case at all. You don't store persistent data in a container. If you care about the data, it's on a backing store that a new container attaches to. You'd have to do something really really weird to update something inside of a container like you're describing.
This is the big one here... think of containers as "throw-a-way". If you have data on there you can't throw away, containers aren't for you. Your data should be elsewhere like he says above.
-
I'm a bit late and haven't caught up. I think a huge piece of this is "Docker is great for specific scenarios" and in turn "awful for other scenarios." Like most good tech, it has a place. It's a strong player. But it is anything but one size fits all, like one would think that it was from how hot it is in the media.
-
@scottalanmiller Mostly this is just @DustinB3403 not having a clue what he is saying.
-
@DustinB3403 : Docker is a specific type of container. It is stateless (can't store data) and as any containers is omogeneous - unless you run it in a VM an entire host must run the same os.
In an SMB usually we have "thick" VM with all layers in (data, business logic, front end maybe) also we have either linux or win on the host.
From a tipical SMB IT Docker is of minimal use.
In bigger envs where your services are split in components and you have a lot of instances running on top of a backing store that make more sense. -
@matteo-nunziati said in Is Docker a joke or do I just not see the point?:
@DustinB3403 : Docker is a specific type of container. It is stateless (can't store data) and as any containers is omogeneous - unless you run it in a VM an entire host must run the same os.
In an SMB usually we have "thick" VM with all layers in (data, business logic, front end maybe) also we have either linux or win on the host.
From a tipical SMB IT Docker is of minimal use.
In bigger envs where your services are split in components and you have a lot of instances running on top of a backing store that make more sense.So Thin VM would be VM that mounts data from network location ?
-
Honestly i don't see much of a point to them but my only exposure to it so far is UNMS. Also i don't fully understand what they do, how they work, how to use them.
Just i ran the command for UNMS and it worked.
-
@emad-r said in Is Docker a joke or do I just not see the point?:
@matteo-nunziati said in Is Docker a joke or do I just not see the point?:
@DustinB3403 : Docker is a specific type of container. It is stateless (can't store data) and as any containers is omogeneous - unless you run it in a VM an entire host must run the same os.
In an SMB usually we have "thick" VM with all layers in (data, business logic, front end maybe) also we have either linux or win on the host.
From a tipical SMB IT Docker is of minimal use.
In bigger envs where your services are split in components and you have a lot of instances running on top of a backing store that make more sense.So Thin VM would be VM that mounts data from network location ?
He's refering to the "thinness" of the workload within the VM, rather than to the state of the VM itself.
-
@hobbit666 said in Is Docker a joke or do I just not see the point?:
Honestly i don't see much of a point to them but my only exposure to it so far is UNMS. Also i don't fully understand what they do, how they work, how to use them.
Just i ran the command for UNMS and it worked.
That's the thing. There's never a point to anything until you have a need for it, and frankly, understand it. Many of you simply have no need for it. That's fine, but it's wrong to say a technology is useless period, rather than useless to you or your company because you have no need or don't understand it.
-
I can explain why Docker is an attractive solution for us. It may not be the same for others.
We create app specific images (web applications) and store these on a registry. I am currently using Swarm so it operates in a cluster that scale up and down as needed. I've got a load balancer that discovers the services automatically with routing rules defined in each service.
This means I can scale up an app in 10 seconds without making any changes other than the scale command. This same ability lets me do app updates without downtime. As long as an app is scaled to at least 2, I can have it update the image by migrating connections away from one, replacing it, and then doing the same to the other.
For DR, I can duplicate our registry to a cloud service and run the stack in almost any cloud service because they all offer some type of container service.
Now this really only works well for our application layer. The data is all stored in databases that use dataguard or other methods of replication for dr/backup/etc.
-
@dsmith said in Is Docker a joke or do I just not see the point?:
I can explain why Docker is an attractive solution for us. It may not be the same for others.
We create app specific images (web applications) and store these on a registry. I am currently using Swarm so it operates in a cluster that scale up and down as needed. I've got a load balancer that discovers the services automatically with routing rules defined in each service.
This means I can scale up an app in 10 seconds without making any changes other than the scale command. This same ability lets me do app updates without downtime. As long as an app is scaled to at least 2, I can have it update the image by migrating connections away from one, replacing it, and then doing the same to the other.
For DR, I can duplicate our registry to a cloud service and run the stack in almost any cloud service because they all offer some type of container service.
Now this really only works well for our application layer. The data is all stored in databases that use dataguard or other methods of replication for dr/backup/etc.
This is interesting.
Can you perhaps show a brief overview or how to in your own thread? Or is this very noob friendly tasks one can do with docker and not worth the effort. Because of this topic i have made a vm with docker enabled and ready to pull images. -
Currently I'm 'using Docker' in Gitlab in order to run unit tests when I make a commit on an application I develop personally. I also my free Gitlab CI/CD minutes to run my application in production... since it doesn't have to run 24/7 I have it scheduled for when it needs to run, so when it's scheduled to run it grabs my Docker image from the registry and runs what it needs to run.
I want to start using docker to start testing Salt config changes I commit on Gitlab. There's a few things I need to get figured out first though, like how to create a Ruby Gem because Kitchen-docker needs some modifications in order to run docker-in-docker. This would be more readily do-able if I was using my own Docker cluster.
At work I'm trying to push for us to start using Docker for Windows, because the current plan for de-coupling our one web service would cost a fair amount of money in Windows Server licences otherwise.
-
@momurda I used this documentation from Docker: https://docs.docker.com/engine/swarm/swarm-tutorial/
I also used this documentation from Traefik which is the load balancer I used in my setup:
https://docs.traefik.io/user-guide/swarm-mode/I ended up making a build machine that the team can share to create images. Harbor is the registry I ended up using to store the images.
I don't think any of the docker parts were too difficult. The harder part is getting the apps into functional images and even that is not too bad once you begin to understand how they work.
-
Hi all,
For an IT, I never really get the grasp of containers, much more its usefulness whereas there's virtual machines.
I know its just me and it is useful for others, just saying that I don't know anything about containers/Docker.
Just chimed in, perhaps someone can give me a light on this (I know its great, useful for others but any usefulness is beyond me).
-
@vhinzsanchez Containers are lighter and faster. And they are a type of virtual machine, Type-C virtualization. So things like performance and density alone are reasons that containers are popular.
