Solve wp-content default permissions #3

Open
opened 2020-09-13 16:30:22 +00:00 by 3wordchant · 0 comments
Owner

wp-content is mounted as a r/w volume, but it's owned by root, which leads Wordpress to think it can't update (it can, all the contents have correct ownership).

It looks like this is a known Docker Compose limitation requiring an addition to the Docker API.

Workarounds include editing the image (no) or using a separate service that just sets up volumes correctly (maybe).

`wp-content` is mounted as a r/w volume, but it's owned by `root`, which leads Wordpress to think it can't update (it can, all the contents have correct ownership). It looks like this is a [known Docker Compose limitation](https://github.com/docker/compose/issues/3270) requiring an addition to the Docker API. Workarounds include editing the image (no) or using a separate service that just sets up volumes correctly (maybe).
3wordchant changed title from Find out why plugin updates aren't working to Solve wp-content default permissions 2020-09-14 16:15:08 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/wordpress#3
No description provided.