Clojurians Log v2

@rahul080327 docker fails on master since today in clj-kondo, any clues? https://app.circleci.com/pipelines/github/clj-kondo/clj-kondo/4576/workflows/72f9a799-f4e0-433c-8d85-8e700c22cd18/jobs/18715

Looks like something happened with the Ubuntu release, will try to take a look tonight!

Thanks, no hurry

Does that run locally? If not try pinning to the older Ubuntu version maybe?

not sure what you mean with running locally

@rahul080327 I naively tried to update the remote docker version because I read somewhere that that may help

@rahul080327 That seems to have done the trick

ah nice! by locally i meant are you able to build the docker image on your local docker and by the looks of it that couldve pointed at the problem too 😄

trying to figure out what the problem was now

my theory for the babashka github release script 404-ing is: the first one seems to fail. then the rest of the jobs succeed and push their artifacts https://app.circleci.com/pipelines/github/clj-kondo/clj-kondo/4590/workflows/4f27d03c-2c9b-4558-937b-4c58efc418ab/jobs/18780 This is why it always happens on a release too since then a new github release is created

also https://ubuntu.com/blog/ubuntu-22-04-lts-released got released so was thinking does that have something to do as the error seems to be some broken packages

not sure how updating docker fixes this

I read something about old docker versions, ubuntu and gpg, upgrading fixed it, so let's just leave it there

interesting, can you send the link? docker versions being tied to what the images are running seems quite weird

quite weird would be a big understatement

I read it on stack overfloew

https://stackoverflow.com/questions/66319610/gpg-error-in-ubuntu-21-04-after-second-apt-get-update-during-docker-build

https://stackoverflow.com/a/66385784/6264

issue in glibc which is manifested via a new feature in apt using the seccomp syscalls... oof 🤯 from the bug tracker:

it this seems to be an issue that there is new functionality in apt/apt-key e.g. security hardening that docker prohibits in its containers. Running this manually works only in an --privileged container.

2 leanings: • static link musl ftw • how does does one apply the clojure non breaking things we try to follow all the way down to the kernel?

so i guess the machine where the remote docker was running in circle updated its OS and we ran into this?

could be

this is too much for my little head to comprehend

well, upgrading fixed it, I'm a happy customer, and was able to release a new clj-kondo ;)

yeah that definitely was the correct fix, what just worries me is that there's no intuitive way for me to figure this out. well another experience then 😅

I think those docker settings were from pretty much the initial commits in clj-kondo

I'm surprised we had macos support from the early beginnings, https://github.com/clj-kondo/clj-kondo/commit/6a253cd6129f7dc06a4f2485af9121b6ffcf09bf I thought you had to have a special circleci support for that, perhaps @marc-omorain enabled that

hmm, something was changed in 2020.10 here: https://github.com/clj-kondo/clj-kondo/commit/15ce36ad616bbc4a86a256719f37145c76372e38

not sure why, no issue number ;)

maybe there's something in our private chats on 2020 October 1st about this

We moved the default docker image to ubuntu on that day: https://github.com/babashka/babashka/issues/604#issuecomment-702302226

(since using alpine as the default lead to many questions)

that's all I could find, not sure why we used a fixed version on that date

i suppose we looking at an example at the time and that wouldve been the version

ive gotten to a pattern of only using raw machine executors and have it all contained in that, not depend on too much external factors

before the commit there was no version at all, using the default

I just read they default to 17 or so now

also these are the reasons tooling like https://github.com/GoogleContainerTools/kaniko were made, do docker image builds in a container in userspace and not do the fancy machine hopping

ah so that version was an upgrade

the version I committed today was an upgrade. but the version I committed on October 1st 2022 was pinning the version instead of using the default and I have no idea what the default was at the time

probably 17 or earlier, if thats still the default now

right