davel comments on Docker Building

Docker Building (lemmy.ml)

submitted 1 year ago by mogoh@lemmy.ml to c/programmerhumor@lemmy.ml

50 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] davel@lemmy.ml 15 points 1 year ago (6 children)

True. Nothing beats running your unit tests in the actual container image that will be run in production.

parent

hideshow 6 child comments

[–] HiddenLayer555@lemmy.ml 9 points 1 year ago* (2 children)

Race condition that only happens on the much faster production hardware: Allow me to introduce myself

parent

hideshow 2 child comments

[–] davel@lemmy.ml 7 points 1 year ago

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.

parent

[–] Qaz@lemmy.ml 5 points 1 year ago

Or an issue that only appears when using ARM and not on my AMD64 dev machine

parent

[–] bjoern_tantau@swg-empire.de 5 points 1 year ago

I mean, isn't that kind of the point of containers? To basically have the same environment everywhere.

parent

[–] qaz@lemmy.world 5 points 1 year ago

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.

parent

[–] bizdelnick@lemmy.ml 1 point 1 year ago

Unit tests? No matter where you run them, and normally this is done by CI in a prebuilt container image, so you don't have to wait for "docker building". Acceptance tests must be run in an environment as close to production as possible, but that's definitely not a programmer's job.

parent