akka / akka-sample-cluster-docker-compose-scala

Apache License 2.0
26 stars 12 forks source link

pull access denied for lightbend/akka-sample-cluster-docker-compose-scala #26

Open elitzer2 opened 5 years ago

elitzer2 commented 5 years ago

Versions used

Using latest code on GitHub as of today 6/4/19 and running docker-compose up

Expected Behavior

The docker containers start up and run as described in README.

Actual Behavior

Error response from daemon: pull access denied for lightbend/akka-sample-cluster-docker-compose-scala, repository does not exist or may require 'docker login'

It seems like the image in the Dockerfile doesn't exist in the Docker Hub?

elitzer2 commented 5 years ago

Ok I was able to run sbt docker:publishLocal and changed the docker-compose.yml to use the image with name of "lightbend/akka-docker" and it worked.

raboof commented 5 years ago

It seems like the image in the Dockerfile doesn't exist in the Docker Hub

That's correct, it's expected to be built from source

changed the docker-compose.yml to use the image with name of "lightbend/akka-docker"

Oh, that should be consistent. Would you be interested in preparing a PR to make sure docker:publishLocal publishes with the name lightbend/akka-sample-cluster-docker-compose-scala?

raboof commented 5 years ago

(I suspect sbt takes the project name from the directory name and you put the project in a folder named akka-docker - so it might just be a matter of explicitly adding name := "akka-sample-cluster-docker-compose-scala" to the build.sbt)

elitzer2 commented 5 years ago

I can try and take a look in the next week. I’m currently in the middle of finishing up my final project for grad school so don’t have much extra time.


Lawrence Elitzer

On Jun 5, 2019 at 1:31 AM, <Arnout Engelen (mailto:notifications@github.com)> wrote:

(I suspect sbt takes the project name from the directory name and you put the project in a folder named akka-docker - so it might just be a matter of explicitly adding name := "akka-sample-cluster-docker-compose-scala" to the build.sbt)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub (https://github.com/akka/akka-sample-cluster-docker-compose-scala/issues/26?email_source=notifications&email_token=ABK5D4OX7XKJVSFMM5OLYPTPY5MVLA5CNFSM4HTNM6QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW6XRMQ#issuecomment-498956466), or mute the thread (https://github.com/notifications/unsubscribe-auth/ABK5D4KKX2L7QSB5HG73VWTPY5MVLANCNFSM4HTNM6QA).

elitzer2 commented 5 years ago

Yup, that fixed it!

elitzer2 commented 5 years ago

@raboof I also noticed some unused import warnings in ClusteringApp.scala. Want me to fix those?

raboof commented 5 years ago

@elitzer2 yes, I'd much appreciate it! (meanwhile closing this issue as #27 fixes it)

alvico commented 5 years ago

I've encountered the same issue, and I don't really know why, it just happened after I removed the images from my local docker repository.

raboof commented 5 years ago

@alvico we don't publish docker images for this example, you're supposed to sbt docker:publishLocal it yourself to your local docker repository.

Perhaps we should not use the lightbend/ organization to make the error message more clear?

alvico commented 5 years ago

thanks raboof, fixed the problem, had several imports messed up due intellij optimise imports... together with the cleaning of the local docker images causes quite a mess in my local project, managed to fix everything and now works faultless. You could close the issue, although I would agree on the suggestion of not using the lightbend organisation.