3 ms·
> We’ve moved far beyond the whole “it works on my computer” thing I dunno. I've had things working on my docker image quite a few times while breaking at the
by marcosdumay 3y ago
> We’ve moved far beyond the whole “it works on my computer” thing
I dunno. I've had things working on my docker image quite a few times while breaking at the deployed one.
This is only passed if you have complete transparency of the entire build and deployment pipeline, total access to the images repository, actual control over the building instructions, etc. That's about as restrictive as control over a local OS, and I do expect it to fail on about as many organizations as the ones that had problems with code breaking when moved into another machine.
- devjab 3y agoAccess to our container registry breaks all the time for no reason anyone has been able to figure out. Not even the third party people we pay a lot of money to help. Basically we now add both a managed ID to the AD group with pull rights, and we setup rights the old fashined way and now it works maybe 95% of the time. Sometimes it still doesn't, and usually the fix is to delete everything and deploy again. As far as actually running the build images, however, if they run in Docker locally then we never have issues with running them in the cloud.