Remote View
How Docker was born
How Docker was born
34 comments
-
It's really great how docker shifted the problem from "works on my machine" to "works with my version of docker".
-
...on my machine.
-
-
Repost #420
Cmon guys, there are less reposted memes on the internet.
-
It's taken me about 6 years to understand how it works and what it does, but I'm finally starting to get it.
I hate software. Why am I in this job still
-
I think most jobs are like this.
The entry level stuff is pleasant and manageable and easy, but if you progress far enough to make money you produce value by managing unsolvable problems which is stressful, frustrating, and difficult.
-
Does managing those problems improve the material conditions of the planet and humanity? If not, then I am not sure you can say it produces value. If you work for a company owned by the 0.1% then your labor does the opposite, the more wealth you create for the oligarchs the more power they have to destroy the planet and democracy
-
-
-
From an administrator standpoint I used to hate containers at first because I was worried about having 3 different versions of a support library on a system all with separate potential vulnerabilities. However we’ve managed to shift our security posture to the left and now all containers are scanned and gated before release approval. This ensures that the devs have the flexibility they want and I have more of the peace of mind of not having to maintain the libraries anymore.
-
-
I love when people say they feel dumb because they didn't know something, because then I get to share xkcd with them, too.
-
-
When the software becomes hardware dependent thanks to a rare and hard to track down bugs, sometimes driver bugs (ask OpenGL developers about their experience with lower-end and embedded hardware!).
-
The biggest problem that I have with docker is honestly, the fear of a supply-chain attack.
-
and that's why you build redundancy and image scanning into your pipeline.
to not use a technology like containers based entirely on a generalization of "security" ignores the obvious security benefits of using a sandboxed environment that can run almost anywhere.
it used to take an hour to release new code into the services I own where I work. with containerized services it takes me five minutes. sure, the builds and scans and qa takes a day but the apps have never been this stable before.
rollbacks would take all fucking night. now? five minutes.
the benefits are a boon to solvency with very little impact to security if managed correctly.
-
but wouldnt that be an issue regardless of docker
-
-
Not far from the truth.
Original 5 minutes reveal from PyCon 2013.
https://www.youtube.com/watch?v=wW9CAH9nSLs
-
I love docker. I also just discovered devpods they have a real nice integration with codium makes by prod and dev environments practically the same.
34 comments