For now, I do not have such problems, because of mac.
I think you could change BUNDLE_PATH for something less like '/app/bundle' not to be a root directory?
Do you also consider to run the docker as non-root user for linux?
Yes, I do it this way now, but annoying bundle folder (though empty) gets created in app directory on host. And still no luck because bundler says / is not writable.
Do you also consider to run the docker as non-root user for linux?
Thanks for the questions, they are really make sense!
1) seems setting it in docker-compose is redundant
2) most suitable place, I think, is to leave the bundle install at bin/setup where it usually is, like here github.com/thepracticaldev/dev.to/...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For now, I do not have such problems, because of mac.
I think you could change BUNDLE_PATH for something less like '/app/bundle' not to be a root directory?
Do you also consider to run the docker as non-root user for linux?
Yes, I do it this way now, but annoying
bundlefolder (though empty) gets created in app directory on host. And still no luck because bundler says/ is not writable.You mean docker command? I run it as non-root, but there's still this issue on Linux github.com/docker/compose/issues/1...
My last set of questions :)
Thanks a lot for your answers!
Thanks for the questions, they are really make sense!
1) seems setting it in docker-compose is redundant
2) most suitable place, I think, is to leave the bundle install at
bin/setupwhere it usually is, like here github.com/thepracticaldev/dev.to/...