This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # announcements (40)
- # aws (2)
- # babashka (46)
- # babashka-sci-dev (106)
- # beginners (31)
- # cider (5)
- # circleci (2)
- # clj-kondo (48)
- # clojure (118)
- # clojure-belgium (1)
- # clojure-chicago (3)
- # clojure-europe (19)
- # clojure-ireland (3)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-spec (10)
- # clojure-uk (4)
- # clojurescript (18)
- # community-development (5)
- # core-async (159)
- # cursive (16)
- # datomic (16)
- # etaoin (1)
- # fulcro (21)
- # funcool (14)
- # graalvm (5)
- # gratitude (4)
- # holy-lambda (28)
- # jobs (1)
- # jobs-discuss (1)
- # kaocha (1)
- # lsp (12)
- # malli (21)
- # meander (12)
- # music (1)
- # off-topic (8)
- # portal (5)
- # react (18)
- # reitit (1)
- # releases (4)
- # remote-jobs (1)
- # shadow-cljs (56)
- # timbre (4)
@cap10morgan the condition https://github.com/babashka/babashka/blob/master/.circleci/script/docker#L47 would never be true right? As we set the var externally to
so yeah I think this is a holdover from the first approach of building each platform separately and then uploading a manifest
Has anyone complained? ;) I ask half in jest as a maintainer of the clojure Docker images who has seriously considered dropping the alpine variants lately.
Well i just stumbled upon it when someone wanted to download alpine images and i could not find the alpine ones for the new versions
last one pushed is 0.7.0-alpine which is the one before our change. alpine would be more useful for bb compared to clojure as mostly they are the final image unlike for clojure where probably the final image is from openjdk or something 😄
Fun fact: we actually had
FROM scratch but then it broke someone's jenkins that expected to have cd at least 😛 then we needed curl to be there too
e.g. does bb need to learn how to resolve platform-specific pods? or would it just be a matter of building and publishing it?
oh never mind, you already answered my question here: https://github.com/babashka/pod-babashka-aws/issues/46
@cap10morgan There is an open issue for pod-babashka-aws and pretty easy to support, just needs the work to be done
@cap10morgan why did we have
linux-foo before and now you are matching on
linux/foo in PR 1141?
@borkdude Just answered on GitHub but I can copy-paste it here: That should have already been in there, but it comes from the fact that docker platform strings look like `os/arch` while GraalVM and babashka use `os-arch`. There was a time when I was using the hyphenated form in this env var, but that was no longer the case by the time the original PR was merged and I just missed converting this one b/c it was never being run anyway.
You'll notice the other platform values (the env var's default and the list we set it to in
.circleci/config.yml) are all
snapshots => babashka/babashka:alpine others => babashka/babashka:<version>-alpine
I need to get this arm64 pod-babashka-aws PR together first, but then I might just take a crack at it 🙂
yep, once I remember how when GH isn't suggesting it :rolling_on_the_floor_laughing:
looks okay to me but what was causing the last error? babashka/babashka:alpine not found one?
oh, d'oh. yeah, b/c it's pushing and not loading now. yeah, you're right, it needs the full command again.
ehhh, yeah. maybe. it's the future and consistent w/ the rest. might even be what you get anyway at this point in the build script given what comes before.
i guess currently it doesnt like things built with buildx and the being pushed seperately
yeah this looks better, TODO was using build and revist when docker is happy mixing buildx and builds
then do you wanna put the above build in the else? its buidling twice now i guess
or it could be cached away :thinking_face: dunno my head spins at these build layer caching nowadays
so for the pod-babashka-aws aarch64 stuff, circleci only provides arm on machine instances, not docker, huh?
looks like the other builds are docker-based, so there's probably some additional work needed there to setup e.g. localstack