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

How to switch to alpine images ? #601

Open
pgera opened this issue Jan 11, 2019 · 8 comments · May be fixed by #2289
Open

How to switch to alpine images ? #601

pgera opened this issue Jan 11, 2019 · 8 comments · May be fixed by #2289

Comments

@pgera
Copy link

pgera commented Jan 11, 2019

I have been using the docker compose files satisfactorily for a while. I noticed that this commit aa5c0c1 changes the images to alpine variants and removes the www-data user from nginx.conf. I tried to pull in these changes, but got a bunch of permission errors in the nginx log, presumably due to the difference in www-data ? My questions are:

  1. Do I need to pull in these changes ? i.e., Would the original images (and their combination) be maintained for nextcloud ?
  2. If it is advisable to change, what is the migration path ? I was reluctant to perturb a working config.
@fuse314
Copy link

fuse314 commented Jan 11, 2019

alpine has different User IDs for the user www-data.
This means, that if you switch to the alpine image, the owner and permissions of the directory /var/www are incorrect.
You need to execute the following command manually to correct this:
docker exec nextcloud_app_1 chown -R www-data:root /var/www (replace "nextcloud_app_1" with your actual app container)
After that, restart the container and the permission errors should disappear.

Make sure that you have the most current "nginx.conf" for your alpine image, otherwise your container will not start with an error... (the first line should NOT be user www-data;!)

@J0WI J0WI added the question label Jan 11, 2019
@pgera
Copy link
Author

pgera commented Jan 11, 2019

Thank you! This worked. Perhaps this should be added as documentation somewhere.

@SnowMB
Copy link
Contributor

SnowMB commented Jan 29, 2019

@pera could you write down your steps and submit a pr?

@pgera
Copy link
Author

pgera commented Mar 11, 2019

The steps are exactly the same as #601 (comment). I can submit a pr, but I don't know where this sort of documentation goes. There isn't an explicit category for this sort of thing. Maybe a new category with important breaking changes should be created where breaking is defined as anything that breaks if you do a git pull in your local install.

@joshtrichards
Copy link
Member

The since added Migrating an existing installation section could probably hold this info under a sub-section.

@alexandra-branco
Copy link

@joshtrichards
Is adding this information still missing from the Migrating an existing installation section?
You can assign me the issue and I will create a pull request for this issue.

@joshtrichards
Copy link
Member

This Issue is still open and it doesn't appear there... So yes.

But there is no need to assign the issue. If you do create a PR, just link it to this issue.

Thanks!

@alexandra-branco
Copy link

PR #2289

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants