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