I understand. Such is life.

i'll set the migration branch up

its either ghcr or http://quay.io from redhat

ghrc is fine with me

is it widely used?

ghcr is the newer one and since its GH/mircosoft based quite the usage now. Quay is older, lesser bandwidth promises but quite consistent.

quay mirrors docker hub now automatically too i think

or should I move those docker images back to my personal account?

not being in dockerhub feels like the right thing to do for me

ok let's do ghrc

yeah should be a safe enough bet

i myself have been using it since last 2+ years

once we do that I'll update the dockerhub organization README that we migrated

i'll read up a bit on the usage limits on ghcr, havent tried a frequently donloaded thing from it

whats a bit off is that say in https://github.com/features/packages#pricing that its 500MB of data storage and 1GB/month transfer limit. I have used it more than that on my public images specially the storage bit. Not sure what happens with bb

We could also just cancel the docker images. People can build their own and download the binary

one thing less to care about

we get questions about those anyway and all we say is: yeah, don't use the minimal, start with ubuntu

oh wait, I think the pricing there is about private repositories on the free plan

for public it's always free

yeah the free bit is there but im concerned about the bandwidth

cant see a number there. cant be unlimited

is that our problem?

it could be if its set at the repo level and not per IP like docker did

My impression is that we don't have to worry with public repos, but could be wrong

yeah thats the hypothesis im trying to prove as well. would be good to make these mistakes now

i'll take a proper look in a bit

as for removing the images altogether, maybe best to ask/poll the users. i think people do use them, things like #C01UQJ4JC9Y i suppose?

right

I guess we can start pushing to ghcr this month and then we have a month before dockerhub pulls the plug

i think ghcr looks good, cant see anything that says it could be limited in anyway. will do a PR tomorrow

hmm maybe I should try this: https://www.docker.com/community/open-source/application/

I applied for cljkondo now

nice, would be nice if this works!

also submitted for babashka now

im doing a test push with a dummy image from my local machine on ghcr, just to check the auth

nice i can reproduce the issue right here

well

guess everyones moving

and that screwed it

aaaah :)

we can run the branch tomorrow again

https://www.githubstatus.com/

yeah 503 status shouldve been the hint. thats generally shit hitting the fan

right. change seems small enough that we can test it tomorrow or next week instead, thanks!

btw, what was the issue with a classic token vs a new token? I can make one

couldnt find the thing that grants package permissions

I'll have a look

there is probably one thats hidden in some obscure corner

im still using the classic one for my things

I'm going to "fine grained tokens" and then... (just am minute, I'm typing as I do this)

generate new token

yeah which one among the list gives package write is where i was lost

decided to get this going and figure that out later

I'll make one and give you the token via DM

can send on https://onetimesecret.com/ too

send me the link on DM

Ah, I think it's not working yet for Github Packages, gotcha https://github.com/community/community/discussions/38467

well, then we just wait

yeah when the infra recovers, can go ahead with the classic token

push works

this is nginx actually: https://github.com/orgs/babashka/packages

deleting and rerunning the docker step

ok, I think the org can be public btw

yeah default is private when its created

ok

looks good: https://github.com/orgs/babashka/packages

$ docker run -it --rm  bb --version
babashka v1.2.175-SNAPSHOT

what about all the other alpine etc stuff?

doesnt push on snapshot

https://github.com/babashka/babashka/blob/master/.circleci/script/docker.clj#L85

should we try this too?

ok, no, I'm convinced it will work....

let's roll back the master / branch stuff and merge

yep

btw wait

does this need a changelog?

why is snapshot lowercase in ghcr? in dockerhub it's all caps

yes, it needs a changelog

well both lower and upper works

thats how the UI is showing it seems

well, uppercase didn't work for me

locally

docker run -it --rm bb --version seems to work for me

oh it did work

it just didn't work for dockerhub in lowercase, kinda confusing

yeah the tag in the registry is in caps

but it's microsoft, of course they have a case insensitive file system :/

thats what the recent pushes show

👍

yeah some windows horseshit

haha

look at what I'm dealing with here: https://github.com/clj-kondo/clj-kondo/pull/2009

heh

tbf, this is also a problem on macos

use linux, like real programmers 😛

Nein Danke

your audio may not work but caps are good

that would be too easy

wanna do a follow up with clj-kondo? should be similar right?

yep

I see we're still on a bash script there and it isn't using buildx

but hopefully the change isn't too difficult

:-s

yeah the multiarch isnt super critical there

wouldve been really cool if we did an actual PR on bb in the workshop

seems a bit for the advanced user

maybe "Babashka advanced workshop 2024"

yeah and this with the PR would be apt for the conj

not following

the unreasonable effectiveness of pull requests workshop like we talked about 😛

haha ok

I merged the PR now

looks good: https://github.com/clj-kondo/clj-kondo/pkgs/container/clj-kondo

awesome!

feel free to undo the undoing of the main branch checks and squash+merge