sbt-native-packager | sbt Native PackagerSBT native packager lets you build | Build Tool library

It looks like you trying to run the docker daemon inside your build image docker run.

For Linux, you need to make sure that the current user (the one running sbt), has the proper permissions to run docker commands with some post-install steps.

Maybe you could fix your script by running sudo sbt docker:publishLocal instead?

It is more common now to use a service to have a docker daemon already set up for your builds:

When you're using the SBT shell you don't type sbt before your commands. If you're on the command line use sbt clean assembly, from within the shell clean assembly is sufficient.

You need to run sbt in the parent directory, not in the project directory, i.e. in C:\...\play-samples-play-scala-starter-example\.

To give more context, SBT is a recursive build tool and the project directory contains metadata to build the main project but it's not aimed to be built directly.

Yes, Docker / dockerExposedPorts is more specific than Zero / dockerExposedPorts. But unlike what you seem to assume, it's the more specific scopes that delegate to the less specific ones, not the other way around. The manual says so:

This feature allows you to set a value once in a more general scope, allowing multiple more-specific scopes to inherit the value.

And in fact, this is the only way it could be, because you might define e. g. both Docker / dockerExposedPorts and Universal / dockerExposedPorts. Which one of these would Zero / dockerExposedPorts delegate to? There's no sensible answer to that, hence delegation goes in the other direction.

This is the first error that looks like a lead:

error: value +: is not a member of sbt.io.PathFinder scriptedClasspath ~= { cp => "modules/" +: "customer-modules/" +: cp }

It says that scriptedClasspath is a PathFinder and you're trying to add elements to it as if it was a Seq[String].

Read the docs on how to work with Path Finders and see the Scaladoc for the PathFinder type.

Most probably you will need to adjust it to something like

The solution was that the build.sbt was missing the version! The version seems to be used as the docker tag!

I only needed to add the version to the top of the build.sbt and the error went away, like this:

You need to inject address of keycloak into your service via environment variable. For this you can use service name as keycloak address (Compose docs)

When running via sbt run, the environment is set by the shell in which you're running sbt. Defining a dev.env file by itself does nothing.

The mechanism for setting the environment in which sbt is running will vary depending on your shell.

For example if bash is your shell (this is worth trying in other Bourne-compatible shells), prefixing the environment variables with export, e.g.:

I was able to resolve my issue with setting up the service module adding job % "compile->compile;test->test"

The whole block looks like: