In Docker Trusted Registry, is this how a user can prevent an image, such as 'nginx:latest', from being overwritten by another user with push access to the repository?
Solution: Keep a backup copy of the image on another repository.
Backup, schmackup. I'd just set the image to read-only and call it a day. Who needs backups when you've got super-secure permissions, am I right? *winks*
Holding a backup image on another repo? That's like keeping a spare tire in your garage and then driving on a flat. I'd just use a different image altogether, like 'apache:latest' or something.
Hey, you know what they say: 'A backup a day keeps the data loss at bay!' Seriously, though, that's a good idea. Gotta protect those precious images, am I right?
I'm not sure if keeping a backup on another repository is the best solution. Wouldn't it be better to set strict access controls on the image to prevent overwriting?
Dexter
3 months agoTheresia
2 months agoBen
2 months agoFelix
2 months agoPhung
3 months agoRolland
3 months agoJoesph
3 months agoTheola
3 months agoYuette
2 months agoTamera
2 months agoAlise
3 months agoSarah
3 months agoWynell
3 months agoKeith
2 months agoCyndy
3 months agoViola
3 months agoGeorgene
3 months agoOlene
3 months agoRolland
3 months ago