Building docker images using sbt-native-packager is the kind of plugin system abuse, that makes me understand why @propensive 's Fury doesn't have one.
-
-
-
Replying to @lukasz_bialy @propensive
If I had a Dockerfile I would know how to do what I want to do. But instead I need to go through the build.sbt and sbt-native-packager'd docs to do simple things. I will have no such problem with Fury ;)
1 reply 0 retweets 1 like -
Replying to @jczuchnowski @propensive
You will most probably come up with your own abstraction over dockerfiles and docker build execution
1 reply 0 retweets 0 likes -
This is something that is still making me itch when I'm thinking about trying out Fury.
@propensive what is your take on complex builds like: build everything, run optimizer or native-image on generated classpath and then build docker image with binary. Bash script?1 reply 1 retweet 0 likes
I'm considering some sort of built-in (not plug-in) support for docker in a later version on Fury. Nothing definite yet, but people often need to do things outside the scope of the JVM, and docker is basically the only way to do that (almost) repeatably.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.