Egregoros

@bajax @phnt if you want to change something in the original dockerfile, just copy and paste it and then make your modifications and then ideally merge it back into the main repo or push it up on your own repo, this is the equivalent of making your own guide, but you can keep running it, when you do docker build it's the equivalent of spinning up a new VPS and doing the installation instructions from scratch automatically, and then you can run tests against it to check if it works. but then you don't have to spin up a second device with a second kernel with docker. that's it, that's all the "bloat" that everyone is complaining about

@shibao @phnt it's a preference thing and you're trying to cast it as some objective truth that you can force people to accept if you just bombard them with more information.

I don't like not having direct access to my executables. I don't like having a central service being the gatekeeper to the environment my software runs in. I don't like having to work with those things outside of my usual environment. I don't like my system suddenly having multiple IPs that I have to manage the security/firewall and routing for (or make sure that the assumptions of the container don't fuck them up for me). it makes messy assumptions about how software even works that a lot of people think is "good enough."

docker does things I don't like. that's all.

@bajax @phnt

>I don't like not having direct access to my executables
you literally just do `docker exec -it container bash` or whatever and you instantly have a shell into the environment. but it's running on your computer, complaining about not having access to things you're running on your computer is crazy. you can even just make changes in this environment but it will be ephemeral if the docker image ever restarts, unless it's part of a host/bind mount. regular volume mounts are literally just storing the virtual filesystem or whatever in /var/lib/docker or whatever

>I don't like having a central service being the gatekeeper to the environment my software runs in
it's not, it's literally just running on your computer like any other executable? do you complain about lvm being a central gatekeeper service for your hard drives?

>I don't like having to work with those things outside of my usual environment.
then don't? my whole point is you can take the items out of the dockerfile if you want but then it's on you to take it out of a dockerfile. most software that isn't total complete dogshit can just be run without docker. if it requires a custom docker image then that's like software that can only run on one guy's machines. we used to have standards and docker doesn't mean we should throw away those standards

>I don't like my system suddenly having multiple IPs that I have to manage the security/firewall and routing for
docker networks basically give you a private VPC on your computer, i think that's better than having some localhost bound port or something that any other service can access on your machine

>it makes messy assumptions about how software even works that a lot of people think is "good enough."
then don't use dogshit software