3 ms·
It seems to me that you should be able to roll back an built via a Dockerfile back to any step in the build, and then rebuild from that point. A deployment vi
by bryanlarsen 13y ago
It seems to me that you should be able to roll back an built via a Dockerfile back to any step in the build, and then rebuild from that point. A deployment via another CM tool would probably lose that ability.
Perhaps it's my inexperience, but I find chef scripts to be very fragile because of the large amount of external dependencies they generally contain. All of these dependencies are very stable: nobody takes down tarballs and packages randomly, but a large number of low probability events can add up to a high probability.
That makes image based deployments appealing, but you still need to have a reliable, repeatable capture of the steps that went into building the image...
- jacquesc 13y agoI've used Chef extensively and found this to be exactly the case. In my experience, going back and running deploy scripts I wrote a year ago have about 10% probability of still working. Aside from chef's breaking changes (and versioning mess), there's a ton of things outside of my control that take things down. Debugging has been a nightmare. I love the concepts and community around Chef, but I've found for my use case, it was an all around bad choice.