/docker/

Because you have to provide it with the libraries it needs and ensure the library will run on the targeted dockerhost machine (i.e. linux).

>But I don't want to worry about library dependencies
So that's why they provide the FROM statement which allows you to base it on a community-delivered "bare-bones" OS

>But that just sounds like a worse type of VM
Yes. Except it spins up slightly faster.

enjoy the pain

VM : you package your application into an executable runnable by the VM.
Docker : you tell all the instruction to run the application, as if you started from a fresh os. So basically a glorified Makefile.

It allows you to build your application's environment with perfect consistency which is great because if you are/were doing that manually then there's going to be something that you don't set up the same exact way every time and you're going to get quirks.
Updating applications is also super easy in that if you want to update or change any piece of the environment, you just edit a text file and rebuild the container. If you're doing compose then you need to edit a second text file and you probably need to push the updated container image to a registry.
Docker Swarm and Kubernetes let you have "muh cloud" high availability and fault tolerance on your own infrastructure with minimal setup.
Containers also use less resources than VMs so you can run more of them on less powerful hardware and save money, and the whole container build and deploy process can be easily automated. While you can automate VM deploy and build, it has in my experience been more convoluted and more difficult.
The biggest problem that I've found with Docker is that by default it fucks with your iptables, but if you're semi-competent you can tell docker not to do that and just do the iptables fuckery yourself.

Attached: fagioli corn munchkin.jpg (2048x1536, 544K)

docker is already dying and being replaced by kubernetes that copied all the good stuff of docker (there wasn't that much)

>asking a bunch of anime watchers instead of just googling it

Should I always run docker+kubernetes on a KVM? Anyone here run it directly on their development machine?

Don't you need containers on kubernetes anyway? How are you going to manage pods without docker?

kubernetes can work with any containerization technology - eg. rkt of coreos
as well docker can run with other orchestration engines (docker swarm would be one of them)

>docker is already dying
imagine being this unemployed
Docker has become, for better or for worse (mostly worse imo), the de facto standard. The big three cloud platforms all advertise Docker support in big bold letters in their whitepapers. The only thing Kubernetes has killed is Docker Swarm. Insofar as AWS and Azure nudge their customers into not using Docker, both promote their own proprietary layers "on top" of Docker like Fargate and App Service.

I use Docker for local development. My host OS (Ubango 18.04 LTS) has neither Python nor Node installed. Instead, I use VS Code with the Remote extension to create custom dev environments as needed. The extension creates and connects to local containers whenever you open a project within VS Code.

VM's are very inefficient and take a long time to boot because they run one OS on top of another OS.

With docker you just have one OS, but with a shielded environment for each container.
The software in the containers runs natively on the main OS, so there is no performance loss and they start near instantly because there is no extra OS to boot.

Anyone tried systemd-nspawn or whatever it's called? Some user on Jow Forums told me about it a while ago, sounded interesting though I never got round to trying it. Supposedly you can do containers entirely on Linux without any extra software.

Kubernetes works with docker containers.

Too complicated.
For small things I just use docker's kubernetes cluster.
For proper dev/test/prod of larger systems, I request a namespace on the organization's cluster.

this
and thank fuck for that.

>imagine being this unemployed
i'm happy being a wagejew thanks to sap, hana
once those move to docker/kube, give me a call

jesus fuck, learn the differences nigger

Docker doesn't do anything special to make reproducible consistent applications. It's just a wrapper program for containers and their configuration.

Don't get me wrong, I've used docker for years. It's made life easier. I like it to reproduce server setups, along with tools like vagrant. Eventually I'll be replacing it with Nix though (on projects where I have that level of control). Docker only does so much, and it was cool when Linux containers we're young, but better solutions are on the way

Containers are great. They are a not a meme and they are here to stay. Despite your edgy hatred on whatever tech trend comes along, containers provide the best solution to a problem that has been plaguing the industry for decades.

To give some perspective, the JVM and Java were pretty much invented to provide a solution to the clusterfuck that was reproducing and deploying software. But then we ended up with JVMs running inside VMs anyway.

Really containers just addressed a flaw in the Unix/Linux architecture as a whole. Ken Thompson unfortunately didn't have the foresight to predict the current world of cloud software. Unix was basically designed to facilitate "sharing". Sharing libs, sharing networking, sharing IO. But this sharing is really the root of the issues that we needed containers to solve.

As to the fate of docker. I dunno. First mover advantage is huge. We are seeing a plethora of alternative container solutions, but its not clear any of them will push through as a winner. Enterprise companies like having an establish brand attached to the software their choose.

I can see Docker being the "Microsoft" of containers. Sure you can get everything they offer in a free/open source alternative. But Docker wraps everything up in a cute box and puts a bow on it for you. And you can throw buzzwords around in your next meeting with upper management to show them how you are staying on top of the latest tech trends, and put the whale logo in your power point slides.

>but what about muh chroot
>what about muh systemd
>what about muh FreeBSD jail
>what about my other obscure linux shit
nah bro. not happening. Companies in general are very conservative about adopting grey beard unix wizard shit. They don't care about your laundry list of technical reasons why its better.

>reddit spacing

Attached: .gif (500x281, 1.59M)

Idrk how it works. Ived used it every day for a year though. My rabbit queue and zookeeper are in it

Kys

Drink bleach and shoot yourself in the mouth, you fucking failed abortion.

Should have just employed Plan 9.

>different perspectives
nigga this is not a pseudo science
read the fucking docker documentation there is everything you need

faggots discover that they can upload tar(1) archives containing an initialization script to a versioned repository and they go nuts and hail it as a resolution. docker(1) downloads those tar(1) archives from the inter-network and runs the initialization scripts inside a chroot. this program was developed because dynamic linking presents a huge problem, as is python 3.

that's the gist. actual implementation may vary.

jesus i should have proofread before posting

Should I use podman or moby instead of docker proper?
I just have a NAS that I want to grab containers from dockerhub for rutorrent/plex/sonarr/radarr/etc

Great explanation, thank you my nigga

Just install these applications normally

You don't need containers

Its easier with containers

It isn't

Just use your package manager jfc

You don't need an entire VM.

rutorrent isn't in the package manager
containers are easier I have done it both ways you won't convince me otherwise

hub.docker.com/r/linuxserver/rutorrent

What's the practical use of Docker? I'm still just a Uni student. The only thing I can guess is to ensure that your program runs on different enviroments.

>Johnny Programmer: "the most recent commit fails to compile - the error mentions a missing library or something but I have the library installed"
>Sally Coder: "¯\_(ツ)_/¯ works on my machine"
Add 300 more developers and you get the above scenario 300^2 times every single day. Docker solves this.

if shared linking creates a problem, then avoid the problem by avoiding shared linking to the extent possible