Fork me on GitHub
#babashka-sci-dev
<
2023-03-14
>
borkdude16:03:16

@rahul080327 I just sent you an e-mail. It seems docker is cancelling organizations unless you upgrade to a team account for 9 dollar per user.. maybe it's time to move away and go to this github docker stuff?

lispyclouds16:03:34

yeah should be easy to move to Github Container Registry, but will be a different URL to pull from

borkdude16:03:49

I understand. Such is life.

lispyclouds16:03:30

i'll set the migration branch up

lispyclouds16:03:05

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

borkdude16:03:14

ghrc is fine with me

borkdude16:03:58

is it widely used?

lispyclouds16:03:13

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

lispyclouds16:03:49

quay mirrors docker hub now automatically too i think

borkdude16:03:43

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

lispyclouds16:03:24

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

borkdude16:03:44

ok let's do ghrc

lispyclouds16:03:28

yeah should be a safe enough bet

lispyclouds16:03:46

i myself have been using it since last 2+ years

borkdude16:03:56

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

lispyclouds16:03:32

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

👍 2
lispyclouds16:03:28

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

borkdude16:03:52

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

borkdude16:03:57

one thing less to care about

borkdude16:03:26

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

borkdude16:03:01

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

borkdude16:03:09

for public it's always free

lispyclouds16:03:23

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

lispyclouds16:03:38

cant see a number there. cant be unlimited

borkdude16:03:50

is that our problem?

lispyclouds16:03:23

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

borkdude16:03:14

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

lispyclouds16:03:46

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

lispyclouds16:03:38

i'll take a proper look in a bit

lispyclouds17:03:32

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

borkdude17:03:30

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

lispyclouds21:03:25

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

borkdude09:03:18

I applied for cljkondo now

lispyclouds09:03:03

nice, would be nice if this works!

borkdude09:03:43

also submitted for babashka now

lispyclouds14:03:36

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

👍 2
lispyclouds14:03:56

nice i can reproduce the issue right here

lispyclouds15:03:47

guess everyones moving

lispyclouds15:03:55

and that screwed it

borkdude15:03:13

we can run the branch tomorrow again

lispyclouds15:03:18

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

borkdude15:03:24

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

borkdude15:03:49

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

lispyclouds15:03:12

couldnt find the thing that grants package permissions

borkdude15:03:19

I'll have a look

lispyclouds15:03:35

there is probably one thats hidden in some obscure corner

lispyclouds15:03:11

im still using the classic one for my things

borkdude15:03:44

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

borkdude15:03:56

generate new token

lispyclouds15:03:32

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

lispyclouds15:03:59

decided to get this going and figure that out later

borkdude15:03:30

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

2
lispyclouds15:03:22

send me the link on DM

borkdude15:03:49

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

borkdude15:03:08

well, then we just wait

lispyclouds15:03:38

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

👍 2
lispyclouds15:03:28

deleting and rerunning the docker step

borkdude15:03:39

ok, I think the org can be public btw

lispyclouds15:03:56

yeah default is private when its created

lispyclouds15:03:51

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

borkdude15:03:14

what about all the other alpine etc stuff?

lispyclouds15:03:26

doesnt push on snapshot

lispyclouds15:03:17

should we try this too?

borkdude15:03:24

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

borkdude15:03:48

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

lispyclouds15:03:35

does this need a changelog?

borkdude15:03:50

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

borkdude15:03:14

yes, it needs a changelog

lispyclouds15:03:04

well both lower and upper works

lispyclouds15:03:16

thats how the UI is showing it seems

borkdude15:03:51

well, uppercase didn't work for me

lispyclouds15:03:17

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

borkdude15:03:46

oh it did work

borkdude15:03:55

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

lispyclouds15:03:15

yeah the tag in the registry is in caps

borkdude15:03:22

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

lispyclouds15:03:26

thats what the recent pushes show

lispyclouds15:03:41

yeah some windows horseshit

borkdude15:03:19

tbf, this is also a problem on macos

lispyclouds15:03:21

use linux, like real programmers 😛

lispyclouds15:03:46

your audio may not work but caps are good

borkdude15:03:46

that would be too easy

borkdude15:03:25

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

borkdude15:03:38

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

borkdude15:03:46

but hopefully the change isn't too difficult

lispyclouds15:03:13

yeah the multiarch isnt super critical there

lispyclouds15:03:22

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

borkdude15:03:28

seems a bit for the advanced user

borkdude15:03:36

maybe "Babashka advanced workshop 2024"

lispyclouds15:03:06

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

borkdude15:03:39

not following

lispyclouds15:03:14

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

borkdude15:03:20

I merged the PR now

2
borkdude16:03:50

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