how to debug a failed start? about sbt-docker-compose

[kurtkopchik]

Hi @fommil - It would be helpful to see the contents of the ruleengine.yml file as well as the full output from dockerComposeUp.

By default the plugin uses the name of the sbt project to determine which service in the yml file is the one being built by the current project. If they differ you need to explicitly set the composeServiceName to be the name of yml service that contains the image being built.

composeServiceName := // Specify the name of the service in the Docker Compose file being tested. This setting prevents the service image from being pull down from the Docker Registry. It defaults to the sbt Project name.

Lastly you should make sure that ruleengine:latest actually exists in the available local docker images. If not, we would need to investigate if (publishLocal in Docker).value is not creating the expected ruleengine:latest image.

[fommil]

it's ok, I got to the bottom of it out of random trial and error. We had dockerRepository in sbt-native-packager and this wasn't picked up by sbt-docker-compose.

I've concluded that we need only a very small subset of the features of this plugin and we need them as Tasks so I'm going to just write something small and use that instead. I can ping you if we make it libre.

Thanks for the inspiration!