Migrating Ruby on Rails application to Docker: Issues with Docker-Compose
up vote
0
down vote
favorite
I'm new to creating my own docker images. I've been following along with this guide. I've successfully built my by using docker-compose build
in the root directory.
However, I encounter the same issue every time I try to run: docker-compose up
I get the following error:
Pulling postgresql (postgresql:latest)...
ERROR: pull access denied for postgresql, repository does not exist or may require 'docker login'
I've setup a docker account. I can run a postgresql image using the documentation.
I'm at a loss as to what to do. I'm thinking I should modify my Dockerfile for my project or the docker-compose.yml file, but I'm unsure.
Also, when I build my app, I get the following at the beginning:
postgresql uses an image, skipping
My docker-compose.yml file looks like:
web:
build: .
command: rails s -e production
ports:
- 3000
links:
- postgresql
- postgresql:postgresql.cloud66.local
environment:
- RAILS_ENV=production
- RACK_ENV=production
postgresql:
image: postgresql
postgresql docker docker-compose
add a comment |
up vote
0
down vote
favorite
I'm new to creating my own docker images. I've been following along with this guide. I've successfully built my by using docker-compose build
in the root directory.
However, I encounter the same issue every time I try to run: docker-compose up
I get the following error:
Pulling postgresql (postgresql:latest)...
ERROR: pull access denied for postgresql, repository does not exist or may require 'docker login'
I've setup a docker account. I can run a postgresql image using the documentation.
I'm at a loss as to what to do. I'm thinking I should modify my Dockerfile for my project or the docker-compose.yml file, but I'm unsure.
Also, when I build my app, I get the following at the beginning:
postgresql uses an image, skipping
My docker-compose.yml file looks like:
web:
build: .
command: rails s -e production
ports:
- 3000
links:
- postgresql
- postgresql:postgresql.cloud66.local
environment:
- RAILS_ENV=production
- RACK_ENV=production
postgresql:
image: postgresql
postgresql docker docker-compose
Have you logged into docker before pulling from the private repo?
– Mark
Nov 8 at 16:31
If so try adding --allow-insecure-ssl to the end of your docker-compose up
– Mark
Nov 8 at 16:32
github.com/docker/compose/issues/1622
– Mark
Nov 8 at 16:32
The official PostgreSQL image is just named postgres.
– David Maze
Nov 8 at 18:39
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm new to creating my own docker images. I've been following along with this guide. I've successfully built my by using docker-compose build
in the root directory.
However, I encounter the same issue every time I try to run: docker-compose up
I get the following error:
Pulling postgresql (postgresql:latest)...
ERROR: pull access denied for postgresql, repository does not exist or may require 'docker login'
I've setup a docker account. I can run a postgresql image using the documentation.
I'm at a loss as to what to do. I'm thinking I should modify my Dockerfile for my project or the docker-compose.yml file, but I'm unsure.
Also, when I build my app, I get the following at the beginning:
postgresql uses an image, skipping
My docker-compose.yml file looks like:
web:
build: .
command: rails s -e production
ports:
- 3000
links:
- postgresql
- postgresql:postgresql.cloud66.local
environment:
- RAILS_ENV=production
- RACK_ENV=production
postgresql:
image: postgresql
postgresql docker docker-compose
I'm new to creating my own docker images. I've been following along with this guide. I've successfully built my by using docker-compose build
in the root directory.
However, I encounter the same issue every time I try to run: docker-compose up
I get the following error:
Pulling postgresql (postgresql:latest)...
ERROR: pull access denied for postgresql, repository does not exist or may require 'docker login'
I've setup a docker account. I can run a postgresql image using the documentation.
I'm at a loss as to what to do. I'm thinking I should modify my Dockerfile for my project or the docker-compose.yml file, but I'm unsure.
Also, when I build my app, I get the following at the beginning:
postgresql uses an image, skipping
My docker-compose.yml file looks like:
web:
build: .
command: rails s -e production
ports:
- 3000
links:
- postgresql
- postgresql:postgresql.cloud66.local
environment:
- RAILS_ENV=production
- RACK_ENV=production
postgresql:
image: postgresql
postgresql docker docker-compose
postgresql docker docker-compose
edited Nov 9 at 7:16
Kimmo Lehto
3,76611228
3,76611228
asked Nov 8 at 16:11
t_wrecks_all
11
11
Have you logged into docker before pulling from the private repo?
– Mark
Nov 8 at 16:31
If so try adding --allow-insecure-ssl to the end of your docker-compose up
– Mark
Nov 8 at 16:32
github.com/docker/compose/issues/1622
– Mark
Nov 8 at 16:32
The official PostgreSQL image is just named postgres.
– David Maze
Nov 8 at 18:39
add a comment |
Have you logged into docker before pulling from the private repo?
– Mark
Nov 8 at 16:31
If so try adding --allow-insecure-ssl to the end of your docker-compose up
– Mark
Nov 8 at 16:32
github.com/docker/compose/issues/1622
– Mark
Nov 8 at 16:32
The official PostgreSQL image is just named postgres.
– David Maze
Nov 8 at 18:39
Have you logged into docker before pulling from the private repo?
– Mark
Nov 8 at 16:31
Have you logged into docker before pulling from the private repo?
– Mark
Nov 8 at 16:31
If so try adding --allow-insecure-ssl to the end of your docker-compose up
– Mark
Nov 8 at 16:32
If so try adding --allow-insecure-ssl to the end of your docker-compose up
– Mark
Nov 8 at 16:32
github.com/docker/compose/issues/1622
– Mark
Nov 8 at 16:32
github.com/docker/compose/issues/1622
– Mark
Nov 8 at 16:32
The official PostgreSQL image is just named postgres.
– David Maze
Nov 8 at 18:39
The official PostgreSQL image is just named postgres.
– David Maze
Nov 8 at 18:39
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
You may be running an outdated version of docker-compose.0
Also, your YAML seems to have an indentation error:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
This should be:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
Maybe it was just a copy & paste error, because the error message implies it was parsed correctly.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You may be running an outdated version of docker-compose.0
Also, your YAML seems to have an indentation error:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
This should be:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
Maybe it was just a copy & paste error, because the error message implies it was parsed correctly.
add a comment |
up vote
0
down vote
You may be running an outdated version of docker-compose.0
Also, your YAML seems to have an indentation error:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
This should be:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
Maybe it was just a copy & paste error, because the error message implies it was parsed correctly.
add a comment |
up vote
0
down vote
up vote
0
down vote
You may be running an outdated version of docker-compose.0
Also, your YAML seems to have an indentation error:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
This should be:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
Maybe it was just a copy & paste error, because the error message implies it was parsed correctly.
You may be running an outdated version of docker-compose.0
Also, your YAML seems to have an indentation error:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
This should be:
web:
build: .
links:
- postgresql
postgresql:
image: postgresql
Maybe it was just a copy & paste error, because the error message implies it was parsed correctly.
edited Nov 9 at 7:23
answered Nov 9 at 7:14
Kimmo Lehto
3,76611228
3,76611228
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53211739%2fmigrating-ruby-on-rails-application-to-docker-issues-with-docker-compose%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you logged into docker before pulling from the private repo?
– Mark
Nov 8 at 16:31
If so try adding --allow-insecure-ssl to the end of your docker-compose up
– Mark
Nov 8 at 16:32
github.com/docker/compose/issues/1622
– Mark
Nov 8 at 16:32
The official PostgreSQL image is just named postgres.
– David Maze
Nov 8 at 18:39