> Tiny correction that got me confused: an exit code of '0' would actually mean 'success', so you probably just meant that it could fail at any moment. No. It

> Tiny correction that got me confused: an exit code of '0' would actually mean 'success', so you probably just meant that it could fail at any moment. No. It fails and then returns 0 = success. It's a design choice. [1] [2] > But also, this can happen any time external servers are accessed, regardless of the tool. An npm install could fail any time without warning, if the servers are down. I think that strengthens my argument that everything should be baked in to the dev container. Edit: Reviewing those bugs, I see there's a new option to control the behavior: -eany, --error-on=any Fail the update command if any error occured, even a transient one. 1. https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900 https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1693900 2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152#15 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776152#15