Andrea Peruffo

I would suggest you to align and upgrade the versions to latest ( 2.0.25 ) and let us know if the problem persists

I agree that those flags should be set by default. Thanks for pointing out @huntc !

The current images are based on Alpine Linux. This PR https://github.com/lightbend/cloudflow/pull/911 eases the path ahead on having "from scratch" base images. We discussed various possible approaches to the problem: -...

Hi @leozilla , thanks for this proposal! For sure implementing support for custom `imagePullPolicy` is something we can take into consideration in our roadmap; if you want to push some...

Thanks for the feedback @leozilla ! Let me try to understand: > I used sbt build instead of sbt buildApp cos this just builds the docker image w/o publishing it....

Thanks a lot for wrapping it up all together @leozilla ! Yes that's more or less how I got it working on `microk8s` as well. We might want to improve...

Thanks for filing this issue! Let me try to go through the different aspects of it. First of all, we do have a "workaround" to separate image building from publishing...

> The build is using `dynVer` plugin to generate the project version This is not mandatory and up to you to enable/disable/workaround if it doesn't play well with your workflow....

@leozilla at the moment you have multiple possible workarounds, e.g. you can define sbt commands or command aliases to package "defining settings + running tasks" (as it's done here https://github.com/lightbend/cloudflow/blob/bafe19d3e3b6f3c35c6b5bc752bce8784f6652a8/tools/build.sbt#L182)....

this has been implemented, can we close?