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

Create a demo docker image #1017

Open
steveyken opened this issue Oct 5, 2022 · 15 comments
Open

Create a demo docker image #1017

steveyken opened this issue Oct 5, 2022 · 15 comments
Assignees

Comments

@steveyken
Copy link
Member

If we have a docker image with demo data loaded, we could use this as a way to 'snap back' the data to a clean state once a day. This would enable the demo to get up and running again.

This was referenced Oct 11, 2022
@johnbumgardner
Copy link
Member

With this demo image, we could set up a demo heroku instance to let people test the app before they clone the repo

@lauriejefferson
Copy link

Is this issue still open? I would like to work on it.

@steveyken
Copy link
Member Author

steveyken commented Jun 5, 2023 via email

@lauriejefferson
Copy link

I forked the repo. Can this issue be assigned to me under 'Assignees'? Thanks.

@johnbumgardner
Copy link
Member

I forked the repo. Can this issue be assigned to me under 'Assignees'? Thanks.

done

@lauriejefferson
Copy link

Your Docker Compose file is pulling an image of postgres:9.5, which according to endoflife.date is deprecated. The official Postgres images on Docker Hub start with version 12.15-bullseye. Is your docker-compose.yml file out of date?

@johnbumgardner
Copy link
Member

johnbumgardner commented Jun 5, 2023

Your Docker Compose file is pulling an image of postgres:9.5, which according to endoflife.date is deprecated. The official Postgres images on Docker Hub start with version 12.15-bullseye. Is your docker-compose.yml file out of date?

it is; go ahead and bump this version

@lauriejefferson
Copy link

Ruby is also out of date. The Dockerfile is using ruby:2.7, which is deprecated according to endoflife.date. The official Ruby image on Docker Hub starts at 3.0-alpine, docker-hub-ruby. Is the Dockerfile up to date?

@johnbumgardner
Copy link
Member

upgrading to Ruby 3.0 is kind of a bigger job. thats on my todo list after finishing the rails 7 migration. for now 2.7 should be fine

@lauriejefferson
Copy link

lauriejefferson commented Jun 5, 2023

I'm having a similar issue as #961 when I run docker-compose. I created the two volumes pgdata and gems and run docker-compose up. Docker can create the /home/app directory, but it hangs on the RUN step and takes a really long time to run the apt-get commands (250s): Here's the error output. Rails doesn't appear to be able to connect to Postgres, from the error on lines 422-425.

@steveyken
Copy link
Member Author

steveyken commented Jun 6, 2023 via email

@steveyken
Copy link
Member Author

Ref PR #1121

@lauriejefferson
Copy link

Steve, I tried setting the env variables to the values in docker-compose, which gave me a new error "could not translate host name "db" to address: Name or service not known". I then tried setting the host: host.docker.internal in the database.postgres.docker.yml file, and got the original "could not establish a connection" error message. I'll continue once PR #1121 is completed.

@johnbumgardner
Copy link
Member

Steve, I tried setting the env variables to the values in docker-compose, which gave me a new error "could not translate host name "db" to address: Name or service not known". I then tried setting the host: host.docker.internal in the database.postgres.docker.yml file, and got the original "could not establish a connection" error message. I'll continue once PR #1121 is completed.

the issue youre experiencing is probably unrelated to the PR Steve is fixing. try deploying the postgres container using docker compose, then creating a side container and seeing if you can use the CLI to resolve the hostname of the pg container. may require tinkering with the docker compose yml

@lauriejefferson
Copy link

@steveyken @johnbumgardner @brynary @olleolleolle Please see PR #1123. Can this issue be closed?

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

3 participants