>mfw docker exists simply because the devs forgot how to build packages

and that's a good thing.

>>105892680
why? i like integration and containers aren't good for this

>>105892676 (OP)
I fucking love docker

>>105892676 (OP)
lol, no
Why does /g/ insist on shitting on technologies just because they are popular? That are popular for a reason.
But sure, let's pretend it is 2001 and you have to run everything directly on the OS. Have fun with that.
Meanwhile I will take my portable Docker images and be 10x more productive than you.

I discard anything that requires docker. whenever I see it mentioned I just close the page don't care what it is.

>>105894902
I used to build packages on Debian 10 years ago. The process was simple: make a chroot, pull dependencies and build.

It's much simpler than doing it with Docker.

>>105895100
And if I want to migrate to RHEL, what then?

>>105895217
Make a chroot, install dependencies, build package. It's the same process on all distributions, even if you wanted to build on Windows through Cygwin you'd do something similar.

In general you cannot build a package from one GNU distribution to another one, although there are tools like Alien and debbuild that try to do just that they usually fail.

>>105895297
>build package for each distribution
vs
>build one docker image

And when using distro package you get the extra fun of having to make sure all software you run on that server don't have conflicting dependencies. Fun times!

>>105895388
Which magical docker image can build packages across different distros?

With docker and with docker I assume you mean container images, i can ship a single file and the user cannot fail to run it no matter how idiot they are or whether they are running some autistic riced distro with case insensitive filesystem. All all need to figure out is docker, the build system and it's simple enough. They need docker, the container engine, to run it but someone else has packaged it already and it's their problem to make it run.
There is overhead but it that means not dealing with weird environments or people, it's proven by the market to be worth it.

The subhumans can't simply build a static binary

>>105894902
Simple: they don't develop software.
/g/ is filled with posers, larpers and lainposters that have never done anything in the industry, and just stick to ricing their shitty linux distro while dilating.

>>105894902
>>105895460
And the docker becomes a new package manager, with the whole operating system becoming the package dependency. You didn't change anything, really, you just made a complex package manager, it is just a new standard, and a more complex with less integration and more difficult to manage (refer to the flatpak desktop problems).
Plus, third-party packages with auto builds aren't a thing because:
1. it was never established by the os maintainers where third-party software can be
2. it was never defined what is the "os" and what is the external software (because packages tends to mix everything)
3. third-party and the os maintainers always fucks up the versioning of their own packages

OP is right. Everything became a container because everyone forgot how to build proper packages.

>>105895829
One thing: i am not against docker or containers in general, the thing is that THERE ARE PLACES for it. Docker is nice to build packages with Dockerfile and that's it. Docker is just a glorified chroot.

>>105895388
>>build package for each distribution
>make a script for each distribution
>run them all at once

>>105895829
>And the docker becomes a new package manage
That's fucking retarded and proves you don't even know what the fuck docker is. Get the fuck off this board you retarded faggot.

>>105895823
The irony being deploying an image means industry collectively gave up on developing a solution (to perhaps an intractable problem admittedly), /g/ is like /v/ in that someone will always defend corporate incompetence or malpractice

>>105895997
Yeah when the average are mediocre lazy fucks it's natural that they'll go to the path of least resistance when it comes to solutions.

>>105892676 (OP)
and kubernetes exists because nobody knows how to manage a docker host or write services that run on it

this is just how IT works, infinite rework

>>105892676 (OP)
I like Docker for setting up canonical build environments. It's nice to have an unambiguous "the code must build in this container with this invocation." This makes reproducible builds easy and means your build environment is not intrinsically tied to any specific machine or cloud service or whatever. I will agree using Docker as a package manager is retarded and no one should be doing that.

>>105896165
I just moved to nix, tired of fucking with CRIs

>>105892676 (OP)
Okay Lain, then show me how you install a high availability cluster for, let's say, gitea
With docker containers, it's three lines
helm repo add gitea-charts https://dl.gitea.com/charts/
helm repo update
helm install gitea gitea-charts/gitea

>>105896270
same for (You)
show me how to do this >>105896481
with nix

But since you guys won't be answering, I'll just point out that helm is pacman for server clusters
no ansible
no terraform
no propietary aws or azure bullshit
just containers on kubernetes

>>105892676 (OP)
Docker is retarded you should use Podman instead but
>always 100% reproducible builds
>you are guaranteed the software will work
>no autistic installation steps
>you are guaranteed the software will run
>you know the software won't shit up (trash files) your system in inexpected ways
>you know the software won't fuck up your system in unexpected ways
>strong security
>very precise control over security, permissons, networking
>very easy control over all data stored by software
>updating software is a single command and you're guaranteed it'll work with no bullshit and no conflicts etc.
Very comfy for servers, software you don't trust
It's only truly necessary for niggers and developers who can't help themselves and use nigger languages (JS, Python, C#, Java)