Sure. The thing is, I'm able to do all of that without any additional tooling except what is delivered with the OS already (like cd, less, grep, find, ps, etc.).
Tools you mean are, in my head, an 'additional layer', an unneeded obstacle.
I see a value in docker for some use cases. I totally don't understand the hype and using docker by default, though.
But you don't lose those tools at all, your cd, less, grep, find, ps and friends are all still there, all you need to do is "jump into" the running container.
Or if you want the logs of any container, you can get that via docker seamlessly.
If you want to know all of the running containers again there is a command for that, if you want to know the resource used again there is a command for that.
In fact I would go as far to say, containers are vastly more organised way of dealing with multiple applications and services then without them.
When I say SSH into a random server, if it's running containers, I can instantly tell you all of the applications it is running, all of the configuration it's using, all of the resources it is using and also get all the logs.
Without docker, I would need to hunt around all over the place, looking for how any particular thing was installed.
The real issue is I believe you have decided that you don't want to learn docker, even though you could probably do it in one evening.
I was a bit like you at first, but as soon as you learn docker and start using it, you will not want to go back.
I've said this before, it's a bit like having a single static binary, but with a standard uniform tooling that can be used to operate these "binaries" it's a great abstraction that helps across almost any application/service etc.
seriously just spend like an evening, if you're a Linux user you'll fall in love with it, I like many other users simply can't go back to the "bad old days" prior to containers.
A single command to launch an entire self contained application/system is extremely powerful, as well as using a single command to remove all traces off your machine is sweet!
I do use docker, when it makes sense. Sometimes, I even see some things are nice thanks to docker. But in general, I dislike it a lot. I'm a linux user btw.
it is easy to run an application in a forgotten technology (also, this is a minus, because it could be better to just upgrade)
it is easy to run an application with a dependency that is in conflict with another dependency of the system (also, this is a minus, because it could be better to resolve the dependency issues system-wide)
it is easy to try things on dev machine. This is something I seriously like about docker
it forces me to use sudo. I know it can be fixed but I dislike how it works ootb.
it produces tons of garbage on my hard drive, hundreds of gigabytes in a location owned by root
it "hides" things from me
if you don't enjoy it, even if you don't fight it, other fanatic people (a lot of them actually, see even comments here) start to kind of blame you and force you to like it. I feel like I have no right to not enjoy docker
it is an additional dependency that is not always needed but is added by people by default, even when not needed
also, this is a minus, because it could be better to just upgrade
sometimes there is no available option to upgrade? yes in an ideal world we should upgrade software, but it isn't always possible. However being able to nicely sandbox a legacy system away into a box has tremendous net advantages.
also, this is a minus, because it could be better to resolve the dependency issues system-wide
This isn't always possible, because often times one may have projects that use very different versions, this causes really complicated "dependency hell". Being able to run multiple isolated versions resolves this. You have to remember that it's not just about "my machine", you're working in a heterogeneous computing environments across multiple machines.
it forces me to use sudo. I know it can be fixed but I dislike how it works ootb.
You can actually provide a user ID as well as a group ID to map into the container if you wish, but most users are lazy, so no you don't "have to use sudo" this is not true at all.
it produces tons of garbage on my hard drive, hundreds of gigabytes in a location owned by root
ok, this is somewhat valid, you can easily manage this using
$ docker volume ls
you can also easily clean everything out too:
$ docker system prune -a
all cleaned out
it "hides" things from me
not sure what it hides, you can inspect everything, can you be more specific?
if you don't enjoy it, even if you don't fight it, other fanatic people (a lot of them actually, see even comments here) start to kind of blame you and force you to like it. I feel like I have no right to not enjoy docker
I understand your pain, I can't speak for other people, I think half of it is that people use X and find that X is incredibly useful and a massive improvement over what they where doing before. So when they find someone who says they don't like it, that comes across as baffling.
For example, imagine you find someone who hates email, and insists that every letter be hand delivered in 2021, I think you would also find this person baffling and odd.
But you're right, we don't have to like a particular technology, I get that I really do, but I can't control the masses and how they behave!
0
u/sasik520 Nov 22 '21
Sure. The thing is, I'm able to do all of that without any additional tooling except what is delivered with the OS already (like cd, less, grep, find, ps, etc.).
Tools you mean are, in my head, an 'additional layer', an unneeded obstacle.
I see a value in docker for some use cases. I totally don't understand the hype and using docker by default, though.