cm0002@lemmy.world to Programmer Humor@programming.dev · 4 months agoHow Docker was bornlemmy.mlimagemessage-square34fedilinkarrow-up1829arrow-down125cross-posted to: programmerhumor@lemmy.ml
arrow-up1804arrow-down1imageHow Docker was bornlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 4 months agomessage-square34fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squarekitnaht@lemmy.worldlinkfedilinkarrow-up20arrow-down1·4 months agoThe biggest problem that I have with docker is honestly, the fear of a supply-chain attack.
minus-squareMrPistachios@lemmy.todaylinkfedilinkEnglisharrow-up5·4 months agobut wouldnt that be an issue regardless of docker
minus-squareDrasla@lemmy.studiolinkfedilinkarrow-up1·4 months agoYou mean compromised code sneaking into Docker images? Or a DOS on dockerhub?
minus-squarekitnaht@lemmy.worldlinkfedilinkarrow-up6arrow-down3·4 months agoSupply chain attack has a definition. And it has nothing to do with DDoS.
minus-squareroofuskit@lemmy.worldlinkfedilinkEnglisharrow-up2·4 months agoThey worry about someone replacing the docker image on the hosting server with a malicious modified version for people to pull down during updates.
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up9·4 months agoThis 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
minus-squareroofuskit@lemmy.worldlinkfedilinkEnglisharrow-up2·4 months agoI was just answering a question. I had the same response above.
minus-squarezalgotext@sh.itjust.workslinkfedilinkarrow-up2·4 months agoAnd I was just adding extra details
The biggest problem that I have with docker is honestly, the fear of a supply-chain attack.
deleted by creator
but wouldnt that be an issue regardless of docker
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
I was just answering a question. I had the same response above.
And I was just adding extra details