jammy doesn't start #20

New Issue

lee.miller · 2022-05-11T01:29:32+02:00

lee.miller commented

2022-05-11 01:29:32 +02:00

Hi!

I cannot found a jammy worker ): https://buildbot.bitmessage.org/#/builders/32/builds/616

Hi! I cannot found a jammy worker ): https://buildbot.bitmessage.org/#/builders/32/builds/616

PeterSurda commented

2022-05-11 01:58:12 +02:00

I think that I misunderstand something and that buildbot sees some multibuild children as duplicates so it skips them. I'll investigate if this is the same bug or something else.

PeterSurda commented

2022-05-11 02:01:07 +02:00

It looks like the same problem. If you rerun the parent manually, it looks like it fixes itself so now we have an output from jammy: https://buildbot.bitmessage.org/#/builders/33/builds/968

lee.miller commented

2022-05-11 02:03:46 +02:00

It looks like the same problem. If you rerun the parent manually, it looks like it fixes itself so now we have an output from jammy: https://buildbot.bitmessage.org/#/builders/33/builds/968

I've seen it locally. You need to update docker. Mine is 20.10.14.

> It looks like the same problem. If you rerun the parent manually, it looks like it fixes itself so now we have an output from jammy: https://buildbot.bitmessage.org/#/builders/33/builds/968 I've seen it locally. You need to update docker. Mine is 20.10.14.

PeterSurda commented

2022-05-11 02:17:02 +02:00

It looks like the same problem. If you rerun the parent manually, it looks like it fixes itself so now we have an output from jammy: https://buildbot.bitmessage.org/#/builders/33/builds/968

I've seen it locally. You need to update docker. Mine is 20.10.14.

Not fully sure how to update docker the best way, probably upgrading the bare metal to jammy would be the easiest but needs testing. I found a possible workaround though:

https://stackoverflow.com/a/71982514

RUN sed -i -e 's/^APT/# APT/' -e 's/^DPkg/# DPkg/' \
      /etc/apt/apt.conf.d/docker-clean

We're running the clean in the buildbot bootstrapper anyway so it doesn't make a difference.

> > It looks like the same problem. If you rerun the parent manually, it looks like it fixes itself so now we have an output from jammy: https://buildbot.bitmessage.org/#/builders/33/builds/968 > > I've seen it locally. You need to update docker. Mine is 20.10.14. Not fully sure how to update docker the best way, probably upgrading the bare metal to jammy would be the easiest but needs testing. I found a possible workaround though: https://stackoverflow.com/a/71982514 ``` RUN sed -i -e 's/^APT/# APT/' -e 's/^DPkg/# DPkg/' \ /etc/apt/apt.conf.d/docker-clean ``` We're running the clean in the buildbot bootstrapper anyway so it doesn't make a difference.

lee.miller commented

2022-05-11 02:34:16 +02:00

https://stackoverflow.com/a/71982514

RUN sed -i -e 's/^APT/# APT/' -e 's/^DPkg/# DPkg/' \
      /etc/apt/apt.conf.d/docker-clean

Yes, I read it. It solved the issue temporary. Need to rebuild the local container to see if it's enough.

> https://stackoverflow.com/a/71982514 > > ``` > RUN sed -i -e 's/^APT/# APT/' -e 's/^DPkg/# DPkg/' \ > /etc/apt/apt.conf.d/docker-clean > ``` Yes, I read it. It solved the issue temporary. Need to rebuild the local container to see if it's enough.

lee.miller commented

2022-05-11 02:55:38 +02:00

No way: https://buildbot.bitmessage.org/#/builders/33/builds/983. It is also a docker bug.