Thanks, very interesting.
This is the current build:
What’s striking is that for Ubuntu only the LTS versions are tested.
So people going on LXD with say Ubuntu 19.04 are in fact living more dangerously that they could think given that most of LXD developers are employed by Ubuntu ! for example this post: not sure if was Digital Ocean’s fault in fact.
Another point is that the tests are done with Alpine containers, because (obviously) it is making for a very quick test, but Alpine is an extremely atypical distro. The test is that a container can be launched, but there could be lot of raisons an Alpine container could be used and not a more classic distro (think systemd, for example - with current Snap on an Ubuntu 18.04 host, a jessie containers don’t start correctly and it’s linked to systemd); Here again people expecting that Ubuntu containers should always be safe are possibly too hopeful. All right, I am pushing it because manual testing by Ubuntu developers is certainly done with Ubuntu distros.
Now, what I really wanted is to find out what is in a given snap. It’s not really obvious since there is no trace of the snap building, but it’s possible to infer that the latest-candidate branch is the one used to build the snap. There is no git release tag :-/. Given the commit dates and the jenkins dates, I have concluded that the pigz change is in the stable channel. Confirmed, pigz is accepted :-). I just have to wait for next backup to see in a real life case how much time is saved. Now for the backup expiration, I think it’s not yet on 10972 given it has been added to the branch only 8 hours ago.