- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or # to comment.
It’s really great how docker shifted the problem from “works on my machine” to “works with my version of docker”.
…on my machine.
I love when people say they feel dumb because they didn’t know something, because then I get to share xkcd with them, too.
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.
Still doesn’t work in production because it’s a multi-cluster k8s instead of a simple laptop
Run a multi-cluster k8s on your notebook to test then?
Good luck, the instances can’t just be started in any random order and at their current version their dependency graph is cyclical.
There’s a solution you’re not seeing, make the notebook part of the production cluster.
The biggest problem that I have with docker is honestly, the fear of a supply-chain attack.
deleted by creator
You mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
Supply chain attack has a definition. And it has nothing to do with DDoS.
deleted by creator
They worry about someone replacing the docker image on the hosting server with a malicious modified version for people to pull down during updates.
This worry exists for literally every 3rd party dependency, not just docker, and is addressed the same way - by running tests and vulnerability scans in a sandboxed test environment before shipping to prod
