- cross-posted to:
- programmerhumor@lemmy.ml
- cross-posted to:
- programmerhumor@lemmy.ml
You must log in or register to comment.
The biggest problem that I have with docker is honestly, the fear of a supply-chain attack.
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.
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
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.
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 really great how docker shifted the problem from “works on my machine” to “works with my version of docker”.
…on my machine.
