=== Eickmeyer5 is now known as Eickmeyer === sem2peie- is now known as sem2peie [11:37] tsimonq2: thanks for sync golang-github-containers-toolbox, could you give-back the builds? it's affected by broken python3-stdlib-extensions in archive. [11:41] and if anyone please give-back golang-golang-x-net as well. (one test is timed out) [11:42] zhsj: I'm assuming by "give-back" you mean retrying the builds? If so, done. [11:43] schopin: yes. thanks [17:09] kanashiro[m]: looking at the new docker.io uploads [17:09] ahasenack: ty! [17:09] why do jammy and kinetic need the additional "-c security.privileged=true", while the older releases only need "-c security.nesting=true"? [17:11] it can't be because focal and bionic launch privileged containers by default, can it? [17:11] bionic was the last one to have lxd as a proper deb, I see. Focal onwards it's a deb-to-snap package [17:12] so focal is using a snap already, let's see if the deb pins a snap version [17:12] otherwise, it will be the same lxd version as jammy and kinetic [17:14] The privileged option was needed just in kinetic IIRC [17:14] correct, just checked [17:14] my question is if the failure without that option isn't the test case telling us something broke? [17:14] I do not know exactly why, but in the other releases it works without that option [17:14] you also have it in lunar [17:15] Yes, >= kinetic [17:15] so the docker version in kinetic right now doesn't need a privileged container, but the new docker does need a privileged container? [17:16] No, it was not a failure as far as I investigated. It did not have the permission to write the image after downloading it [17:16] s/container/lxd/? [17:16] No, right now it needs a privileged container, that is why it is failing :) [17:16] Adding it fixes the test [17:17] This test failure has been happening since jammy [17:18] but jammy doesn't need the privileged lxd [17:18] Not because of the privileged container but because of lxd not being available as a deb [17:18] ok, so we never got that far [17:18] (how did it migrate...oO?) [17:18] After fixing the lxd installation we would get this [17:19] It migrated because it was already failing, so no regression [17:19] But yeah, not sure when this started to happen [17:21] where is the kinetic failure due to lxd not being available? https://people.canonical.com/~ubuntu-archive/proposed-migration/kinetic/update_excuses.html#docker.io is clean for the version in kinetic-proposed [17:22] Not sure about excuses, I reproduced it locally [17:22] Autopkgtest execution is the test plan for the SRU [17:23] https://people.canonical.com/~ubuntu-archive/pending-sru.html also doesn't show it [17:23] but it does show errors elsewhere, in focal [17:23] docker.io in focal, in a dependent set of packages [17:26] ok, so kinetic is all red: https://autopkgtest.ubuntu.com/packages/d/docker.io/kinetic/amd64 [17:27] why isn't that in the reports... [17:27] "E: Package 'lxd' has no installation candidate [17:27] " [19:39] sil2100: hi there, I'm getting "Error 500" when accessing bileto, and it tells me to ping you, so here I am :)