Fork me on GitHub
#babashka-sci-dev
<
2023-02-06
>
lispyclouds10:02:05

looks like a ubuntu mirror issue not docker, can retry

lispyclouds10:02:30

the issue is coming from trying to run apt update

borkdude10:02:34

I've already retried

lispyclouds10:02:28

yeah fairly sure its a ubuntu mirror thing.

lispyclouds10:02:19

this depends on things like source ip and mirrors etc, not sure of a definite way to fix this

borkdude11:02:16

do you think it will resolve itself?

lispyclouds11:02:09

Yeah one of the retries might resolve it. These things unfortunately rely on non immutable registries

lispyclouds11:02:47

Maybe we could use a curl docker image rather than Ubuntu

borkdude11:02:00

I'll just wait a few hours

lispyclouds16:02:00

is it a circle ci thing?

lispyclouds16:02:15

does the same pass in actions?

lispyclouds16:02:34

i can try to have a look in a bit, not around the machine

borkdude16:02:21

I can reproduce it when going manually to http://archive.ubuntu.com/ubuntu/pool/main/z/zlib/zlib1g-dev_1.2.11.dfsg-2ubuntu1.5_amd64.deb - sometimes it works, sometimes it doesn't. It seems their infra might be a bit sketchy?

lispyclouds16:02:04

yeah its almost always that. depends on where the mirror lands you and your IP getting banned etc or not

borkdude16:02:24

but it's happening today a lot whereas it hasn't happened in a long time

borkdude16:02:45

guess we'll need to move to nix for everything sooner than later :P

lispyclouds16:02:01

id try asking in #CJR0NB4MS too

lispyclouds16:02:41

another option could be us vendoring in base images in our dockerhubs and always FROM those

borkdude16:02:25

solve one flaky test, get another flaky ubuntu thing

lispyclouds16:02:06

this is the reason people like me have jobs