Sam Ruby

When I run demo 3 from https://github.com/rubys/dockerfile-rails/blob/main/DEMO.md on a Mac, I'm not seeing that. I'm only seeing files owned by me. Can you try that demo? ``` % ls -ld...

I've reproduced the problem. [this post](https://pratikpc.medium.com/use-docker-compose-named-volumes-as-non-root-within-your-containers-1911eb30f731) suggests a workaround. I'm traveling this week so it may be a few days before I am able to fully test a few.

[dockremap](https://gist.github.com/heyfluke/b8372df866ec2584f9a51ca7d7fe9ebb) also looks promising

If volumes are better, then I'm fine with switching to volumes. If the answer is "it depends", I'm fine with it being an option. It seems to me that with...

> I don't think that's the problem here My apologies. I was unclear. What happens if you generate a docker compose file for one app, and later generate a docker...

Would you consider making a pull request? The tmplate can be found here: https://github.com/rubys/dockerfile-rails/blob/main/lib/generators/templates/docker-compose.yml.erb Running `rake test:capture` will update the expected test results to match your changes. Run `git diff`...

This will require dockerfile-rails to check for and parse the `fly.toml` file, which will be fly.io specific; that being said, I see no reason why this couldn't be done.

Try without the cache option? The way dockerfile caches work is that they are on a separate volume that is mounted only for that one step.

I'm assuming that you are running off of `main` as that hasn't been released? Not documented very well, but `--sudo` will make the whole `/rails` tree owned by `rails`

It looks like the following does *not* give ownership over `/rails`, just the files in that directory: ``` COPY --from=build --chown=rails:rails /rails /rails ``` I'm leaning towards adding an option...