btw, my bug request got accepted https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8275838

will try babashka-curl approach

raised https://github.com/lispyclouds/contajners/issues/3

Another alternative I forgot to mention: shell out to Docker CLI, parse JSON response

If I can avoid docker cli that would be nice - the client is not that great (needs a LOT of TLC IMO ). Also I would like to create secrets from vault without writing them to disk and docker-cli would complicate this.

@borkdude theres no harm in having bb incompatible/java deps in my deps.edn and my classpath to load the lib into bb right? its an issue only if i require/import them right?

im thinking should we be making the things in deps.edn conditional too or not

@rahul080327 currently bb only loads deps from bb.edn

right, but if i use (babashka.deps/add-deps ...) with a lib with deps edn, would bb construct the classpath from its deps.edn?

you can see this with:

$ bb -cp "" -e "(babashka.deps/add-deps {}) (babashka.classpath/get-classpath)"
""

ah right, so its fine to have non compatible things in the deps.edn then, thanks 😄

where is babashka.deps/add-deps taken from ? I can't find the lib

it's built into bb