When you want to solve one problem and create bazillions of new problems in the process (log management, monitoring...

>when you want to solve one problem and create bazillions of new problems in the process (log management, monitoring, storage, security, tracing, etc...)
Who let this happen?

Attached: docker_facebook_share.png (336x287, 4K)

How would you resolve the "Works on my machine" meme otherwise OP ?
Don't want to insult you, you are probably a very good person at heart, but you sound like a fucking brainlet who never put a real huge application in production.
Docker is to deployment what Git is to versioning.

It is pretty solid imho.
Of course, it takes some time to get your full stack running, but with it's universal adoption it's pretty easy to find some good documentation on it.

Attached: 4b8a183903cd9a2e64325880ab3c57b1.png (287x431, 91K)

INB4 Le Docker shill triggered xDDD
t. samefag

Attached: 49a9308b0dcb9d340704931b1d11043c.jpg (500x521, 31K)

>How would you resolve the "Works on my machine" meme otherwise OP ?
Use a managed language?

You mean like Java ?

Attached: 1534865666344.png (1200x1400, 502K)

> How would you resolve the "Works on my machine" meme otherwise OP ?
By not writing shit code.
> Docker is to deployment what Git is to versioning.
Pretty bold, considering Docker Compose can only roll out Docker containers and not, for example, somethnig KVM- or VMWare-based.

I put fucking parts of the fucking Airbus Ressource Management System into production. You will never put something as big in production EVER in your WHOLE life.
It's SAP tho'.

Also I confess I'm a brainlet but the size of my brain doesn't matter; you solve the "Works on my machine" meme with competent developers, conditional compilation and configuration script. Seriously.

The problem solved by docker is the following: "short time to market X lack of competent developer"s not the "Works on my machine" problem. Anyway, Docker require: virtualization solutions and configuration script and a lot of other shit, the scripts are just shorter and in an unified format.

>Current year; not using Qubes.

It's like you want fucking glow in the dark CIA niggers all up in your shit.

Attached: Muttley.gif (320x210, 836K)

If you want to use VM stop being a shitlord and use them. Docker containers are actually industry standard and it's great for me.
Docker was created to stop using VMs because containers are smaller and have better security since they can only host your app (alpine images) and not whole os. Imagine starting a whole bunch of VMs for your pipeline after a push to repository and then waiting few minutes. Containers will start in few seconds and you're done. Also they're stateless so you don't need to clean up.

I don't understand the point of docker.

> Docker containers are actually industry standard
That means you've been on that side of the industry, that's all.

Yeah, on the cloud side

To make devs and sys admins even lazier

I work a lot with vert.x and postgresql. I do that shit on my main machine and when I'm finished, I set up a server and move that shit over there. How would docker help me now?

It allows you to create container environments where your application runs so you can easily deploy a working environment that is identical for all customers. Basically it mitigates the "works on my machine" thing, where some customer have .NET 4.5 while others are on 4.7 which might cause problems. Or a customer has XYZ configured globally on their server for another vendor, and with XYZ enabled your application gets fucked in the ass due to unforeseen issues.

Makes it easier to develop since what you see is what you get, both on the local developer machines and the target customer's server.

Unless you're a blazing faggot like most people in this thread who think they can code in Cobol and hate web development because it is the new norm and love to make shitty installer applications to install their infrastructure to the customer's server that always are bound to fail 70% of the time.

t. CS college freshman major

In the real world, you will not be working in some super sanitized academic environment where everything "just werks." There are environmental considerations that cannot be solved by simply writing "better code." Even the smallest projects can have numerous moving parts; if one of those moving parts is 2 versions behind in your production environment, it could fuck everything. Docker ensures that your environment travels with your code so that you don't have to spend weeks figuring out why feature X is suddenly broken.

Sysadmins.
They always need to create new, very long term problems in order to not become redundant.

Now let's just hope x86 never dies, or else all these containers will be worthless.

We've reached a point were it's unimaginable that software would just run on a machine. Like that's just so outrageously impossible that "ship it in a vm" is a solution.

Attached: thisisfine.jpg (326x154, 21K)

Jails were first introduced in FreeBSD version 4 on 14 Mar 2000.

Or you could just run a VM like normal people do.

>VM
Waste of resources

>containers are smaller and have better security since they can only host your app
How about escaping the container? How about the fact that even if you think you're performing an operation without root privileges, you actually end up communicating with dockerd which does have root privileges? Note: I don't know a shit about it, these are the points that somebody more knowledgeable than me brought up when asked about docker.

How about NixOS? Doesn't its reproducible configuration solve the "works on my machine" problem? I know it's still immature.

Attached: special-snowflake.png (1183x1024, 88K)

An application's environment encompasses more than its operating system.

And boot up an entire guest OS for each application? No thanks.

Yes, it does. Your point? I suppose you don't realize that NixOS configuration includes packages and I think that's the kind of environment you're talking about.

You boot it up and let it run until the end of days.