This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-14
Channels
- # announcements (10)
- # architecture (3)
- # atom-editor (1)
- # babashka (53)
- # babashka-sci-dev (118)
- # beginners (74)
- # biff (10)
- # calva (13)
- # clara (13)
- # clerk (20)
- # clj-commons (17)
- # clj-kondo (6)
- # cljdoc (19)
- # cljs-dev (3)
- # clojars (2)
- # clojure (63)
- # clojure-art (2)
- # clojure-europe (68)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-uk (3)
- # clojured (19)
- # clojurescript (34)
- # clr (1)
- # cursive (11)
- # emacs (12)
- # fulcro (3)
- # helix (2)
- # holy-lambda (2)
- # honeysql (27)
- # hyperfiddle (36)
- # malli (2)
- # off-topic (72)
- # polylith (4)
- # rdf (20)
- # re-frame (20)
- # reitit (4)
- # rewrite-clj (14)
- # shadow-cljs (17)
- # slack-help (2)
- # tools-deps (36)
- # xtdb (3)
Who here is using the babashka docker images on dockerhub? Due to circumstances we can't use dockerhub for organizations in the near future.
We're considering two options:
1. Remove support for them altogether. just build your own image and download the appropriate binary in a RUN
step
2. Move to ghcr registry (Github packages).
If you have any thoughts on this, please reply in 🧵
I'm reading https://docs.github.com/en/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility: > Public packages allow anonymous access and can be pulled without authentication or signing in via the CLI
yeah public access works
Since babashka is on nixpkgs, there’s always https://nixery.dev (at least for dev purposes)
or maybe @U06FS3DLH could consider having a bb flavour in https://hub.docker.com/_/clojure 😄
it's been discussed! https://github.com/Quantisan/docker-clojure/issues/129 🙂
was just waiting to see if there were a compelling need for it. maybe this is it?
@U04V15CAJ care to elaborate on the circumstances (either here or in DM)?
@U04V15CAJ how does clojure:babashka1.2.174
look to you?
@U06FS3DLH I'm on docker organizations (babashka and clj-kondo) and I'm not going to pay 9 dollars for each member in those organizations
ah, gotcha. yeah, gross
@U04V15CAJ If you wanted to, I bet we could make you a co-maintainer of the bb variants in the official image.
or we could take it on, that'd be fine w/ me too
the clojure ones are multi arch too, @U06FS3DLH the one who did the work in bb 🙂
yep, we're good to go for all that
i can volunteer for maintenance of that too if you like @U04V15CAJ but it comes down to if we are combining clojure/jvm and bb here
@U06FS3DLH I can add in the context for the need on the issue if you want
@rahul080327 yeah, thanks! Can you tag the repo owner to be sure he gets a ping?
He's in here somewhere too. 🙂 @U054P6SA8 any thoughts on ^^^?
@U04V15CAJ yeah, I do that manually when new releases are made currently. but we could throw some GitHub Actions at it to automate too.
i can pair on that too, good reverse contrib from me i think 😛
me too! 😅
If you all think this makes sense in terms of tooling, then go ahead please. Plus, I read that we're getting more maintainers for docker-clojure! 🎉 Thank you!
IMHO,
As a product, I can see it make sense. docker-clojure provides images for entry points to Clojure. Many users use bb
to use Clojure to replace bash. In that sense, it doesn't seem too far of a stretch to provide bb
variant in docker-clojure.
Technically, I just had a look at babashka/Dockerfile and related files in script/
, installation seems involved. So it's a non-trivial addition to the docker-clojure codebase. Stating the obvious, we need to keep each variant's footprint clean and minimal, and the codebase easy to maintain. As noted in this thread already, integrating bb
might be a good reason to make some progress on those goals for docker-clojure that'll benefit everyone.
@U04V15CAJ What are limits on ghcr? Isn't there some limit on storage size or so?
@UBLU3FQRZ its the same doubts i had but i dont see any limits being mentioned anywhere for open repos. all seem to be for private repos
I applied here now https://www.docker.com/community/open-source/application/ for both bb and clj-kondo, we'll see
If I won't have an answer within a week, we'll go forward with what people think is best here
Luckily chose nbb
on a node
image, issue bypassed. 😅
Similarly it's very easy to start off with a ubuntu or alpine image, install curl and just download the binary 🤷
After reading this I would say, screw docker and let's move to ghcr, regardless if they will grant the OSS excemption. https://blog.alexellis.io/docker-is-deleting-open-source-images/
We can leave those dockerhub things running as long as they support it but meanwhile people can migrate to ghcr
im on the same page too, but would you wanna give the bb+clojure image route a shot as well?
not sure of it, yeah can get the ghcr going and then do that in later
we'll be moving docker images to ghrc: https://github.com/orgs/babashka/packages/container/babashka/versions thanks @rahul080327
As a side note to this issue I have moved all my docker installs to podman as a result of this. The fact that docker won't let you easily change the default artifact repo was the last straw for me. Podman is pretty awesome and offers many more features, and is fully open source. There is even a podman-desktop cask in homebrew that has replaced docker desktop for me.
wrote https://github.com/lispyclouds/contajners just from the same love too. just waiting for buildx like multiarch support without all the buildah dance and im ditching docker fully too.
we'll be moving docker images to ghrc: https://github.com/orgs/babashka/packages/container/babashka/versions thanks @rahul080327