4 ms·
You are confusing two different things. One is using Docker as a deployment packaging method. The other is using Docker only for development and still deployin
by kkapelon 6y ago
You are confusing two different things.
One is using Docker as a deployment packaging method.
The other is using Docker only for development and still deploying traditionally. Sure you can do both, but it doesn't have to be this way.
>when I use Docker, I pretend it's a VM
Also check anti-patterns 1 and 4 here
https://codefresh.io/containers/docker-anti-patterns/ https://codefresh.io/containers/docker-anti-patterns/
- gspr 6y agoAnti-pattern 1 perfectly describes how I am (hamfistedly) using Docker. Thanks! However, it doesn't really explain how to fix my mindset. It just says that I should ;-) Could you give me some hints?
- kkapelon 6y ago"There is no easy fix for this anti-pattern other than reading about the nature of containers, their building blocks, and their history (going all the way back to the venerable chroot)." Basically learn the basics (cgroups, namespaces) You should also study this https://github.com/p8952/bocker https://github.com/p8952/bocker
- gspr 6y ago> Basically learn the basics (cgroups, namespaces) I think I have a basic grasp of those things, but still don't get how Docker uses them. > You should also study this https://github.com/p8952/bocker https://github.com/p8952/bocker Cool! That's very usefl!
- darkteflon 6y agoThis is an important distinction and one that sometimes gets lost in the back-and-forth over Docker. I feel like a lot of the complaints levelled at Docker pertain to the packaging and deployment use case. Where Docker really shines - even for small teams or solo devs - is as a development tool.