mogoh@lemmy.ml to Programmer Humor@lemmy.ml · 2 months agoDocker Buildinglemmy.mlimagemessage-square47linkfedilinkarrow-up11arrow-down10cross-posted to: programmer_humor@programming.dev
arrow-up11arrow-down1imageDocker Buildinglemmy.mlmogoh@lemmy.ml to Programmer Humor@lemmy.ml · 2 months agomessage-square47linkfedilinkcross-posted to: programmer_humor@programming.dev
minus-squaredavel@lemmy.mllinkfedilinkEnglisharrow-up0·2 months agoTrue. Nothing beats running your unit tests in the actual container image that will be run in production.
minus-squareqaz@lemmy.worldlinkfedilinkEnglisharrow-up0·2 months agoYeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up0·2 months agoI mean, isn’t that kind of the point of containers? To basically have the same environment everywhere.
minus-squareHiddenLayer555@lemmy.mllinkfedilinkEnglisharrow-up0·edit-22 months agoRace condition that only happens on the much faster production hardware: Allow me to introduce myself
minus-squaredavel@lemmy.mllinkfedilinkEnglisharrow-up0·2 months agoUnit tests can’t win ’em all. That’s where things like integration tests, staging environments, and load testing come in. The final layer of protection is the deployment strategy, be it rolling, canary, or blue-geen.
minus-squareQaz@lemmy.mllinkfedilinkEnglisharrow-up0·2 months agoOr an issue that only appears when using ARM and not on my AMD64 dev machine
True. Nothing beats running your unit tests in the actual container image that will be run in production.
Yeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.
I mean, isn’t that kind of the point of containers? To basically have the same environment everywhere.
Race condition that only happens on the much faster production hardware: Allow me to introduce myself
Unit tests can’t win ’em all. That’s where things like integration tests, staging environments, and load testing come in.
The final layer of protection is the deployment strategy, be it rolling, canary, or blue-geen.
Or an issue that only appears when using ARM and not on my AMD64 dev machine