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

rake docker:build fails because of root access rights on frontend container. #16114

Closed
gl-yziquel opened this issue May 9, 2024 · 4 comments
Closed

Comments

@gl-yziquel
Copy link

Issue Description

I just checked out master (f60852d) on github's open-build-service, looked at CONTRIBUTING.md and, accordingly, ran rake docker:build.

It fails because, in the frontend container, the rake dev:bootstrap RAILS_ENV=development command that issued via docker compose expects to write a file in config/database.yml copied from the homonymous (with .example suffix) without the sufficient access rights to create the file. Only root may write, but not frontend.

The CONTRIBUTING.md instructions fail because of that.

Expected Result

The rake docker:build command should succeed, and the config/database.yml file in the frontend container should be correctly scaffolded.

How to Reproduce

  1. Clone the git repo on github called open-build-service
  2. Initialise the git submodules.
  3. run rake docker:build

Further Information

I am running docker rootless. But I doubt this is the reason for the failure.

@hennevogel
Copy link
Member

The setup is supposed to be run as user. How did you run this, please share the exact steps. Additionally share the content of docker-compose.override.yml and the output of id -u of the user you ran this with.

@hennevogel hennevogel added Frontend Things related to the OBS RoR app and removed Frontend Things related to the OBS RoR app labels May 13, 2024
@danidoni
Copy link
Contributor

@gl-yziquel can you share how did you run this so we can debug it a bit more?

@gl-yziquel
Copy link
Author

@gl-yziquel can you share how did you run this so we can debug it a bit more?

Not enough time, unfortunately. If I find time to come back to it (which I really want), I'll give out more info. Meanwhile, if the bug report is not precise enough, feel free to close it.

@danidoni
Copy link
Contributor

Not enough time, unfortunately. If I find time to come back to it (which I really want), I'll give out more info. Meanwhile, if the bug report is not precise enough, feel free to close it.

Alright, feel free to open it again when you have the time!

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