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

Dependency persistance #26

Open
paranormalhacktivity opened this issue Jun 17, 2021 · 3 comments
Open

Dependency persistance #26

paranormalhacktivity opened this issue Jun 17, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@paranormalhacktivity
Copy link
Collaborator

"If you manually run docker-compose run app bundle install, but then docker system prune, the newly installed gems don’t persist unless you build. Maybe this is expected Docker behavior though?" - @evanthegrayt

@paranormalhacktivity
Copy link
Collaborator Author

paranormalhacktivity commented Jun 17, 2021

If a docker container is down, which in our case it would be since we never really go 'up' with it, the docker system prune will remove the container and images in it’s entirety, but with newer versions of docker, they removed the ability for docker system prune to remove volumes unless passed the --volumes option as well, which should mean that they would persist since we've added the planter_bundle_cache volume. One thing I am noticing, is that the only thing in /bundle_cache is ruby/3.0.0 which could be why none of the other dependencies persist. Adding one more thing for reference here, gems are being stored at /usr/local/lib/ruby/3.0.0. I feel like it could be the case that we need to potentially move those over to the /bundle_cache directory that is being used as a volume. Definitely worth exploring that train of thought.

@evanthegrayt
Copy link
Owner

If a docker container is down, which in our case it would be since we never really go 'up' with it, the docker system prune will remove the container and images in it’s entirety, but with newer versions of docker, they removed the ability for docker system prune to remove volumes unless passed the --volumes option as well, which should mean that they would persist since we've added the planter_bundle_cache volume. One thing I am noticing, is that the only thing in /bundle_cache is ruby/3.0.0 which could be why none of the other dependencies persist. Adding one more thing for reference here, gems are being stored at /usr/local/lib/ruby/3.0.0. I feel like it could be the case that we need to potentially move those over to the /bundle_cache directory that is being used as a volume. Definitely worth exploring that train of thought.

Love it dude, thanks for the write up!

@evanthegrayt
Copy link
Owner

How that #27 is merged, we need to see if this issue is fixed.

@evanthegrayt evanthegrayt added the bug Something isn't working label Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants