Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error running docker-compose #54

Open
jeffslofish opened this issue Jul 9, 2019 · 4 comments
Open

Error running docker-compose #54

jeffslofish opened this issue Jul 9, 2019 · 4 comments

Comments

@jeffslofish
Copy link

I am trying to get all set up and this is what I run into. Do I need special permissions to use docker?

Jeffreys-MacBook-Air:p2p-lending jeff$ docker-compose run web python manage.py createsuperuser
Pulling migration (app:)...
ERROR: pull access denied for app, repository does not exist or may require 'docker login'
@nikolajbaer
Copy link
Member

nikolajbaer commented Jul 9, 2019

What is the result if you run:

docker-compose build

Does that successfully build an image?

Edit: I did a bit more googling, and it appears that the error is caused when you don't have access to the base images. However in this case "app" extends the local Dockerfile, which in turn pulls from "python:3.7" and "node", which as far as I can tell are public images. I am not logged-in on my Docker daemon locally.

What are the versions of Docker / Docker Compose that you are running?

@jeffslofish
Copy link
Author

docker-compose build doesn't work eitiher:

(p2p-lending) Jeffreys-MacBook-Air:p2p-lending jeff$ docker-compose up
Pulling migration (app:)...
ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]

I'm running Docker version 18.09.2, build 6247962 and docker-compose version 1.23.2, build 1110ad01

@jeffslofish
Copy link
Author

Update: I got it working by running docker build . -t app first.

@nikolajbaer
Copy link
Member

Ok, I was able to get the same error if i started deleting images from my local docker. I am not entirely clear on the issue, but i will see if i can get it going on a blank install at some point to see if our upstream images maybe have a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants