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

Add "--no-overwrite-dir" to "tar" invocation for running as an arbitrary user #351

Merged
merged 2 commits into from
Nov 28, 2018

Conversation

tianon
Copy link
Member

@tianon tianon commented Nov 27, 2018

This fixes tar: .: Cannot utime: Operation not permitted and tar: .: Cannot change mode to rwxr-xr-x: Operation not permitted (which we get currently).

This combined with docker-library/php#755 fixes part of what @wglambert noted in docker-library/php#754 (comment).

…ary user

This fixes "tar: .: Cannot utime: Operation not permitted" and "tar: .: Cannot change mode to rwxr-xr-x: Operation not permitted" (which we get currently).
@tianon
Copy link
Member Author

tianon commented Nov 27, 2018

(Added another fix for APACHE_RUN_USER=#xxx syntax.)

@yosifkit yosifkit merged commit a748aaf into docker-library:master Nov 28, 2018
@yosifkit yosifkit deleted the no-overwrite-dir branch November 28, 2018 00:03
tianon added a commit to infosiftr/stackbrew that referenced this pull request Nov 28, 2018
- `ghost`: 2.6.2, more arches (thanks to nodejs/docker-node#921)
- `joomla`: 3.9.1
- `matomo`: php-apcu to 5.1.14 (matomo-org/docker#125)
- `openjdk`: `7u181-2.6.14-2~deb8u1`
- `php`: fix arbitrary user permissions (docker-library/php#755)
- `postgres`: `dpkg-divert` config file for correctness (docker-library/postgres#529)
- `redis`: 5.0.2
- `wordpress`: add `--no-overwrite-dir` for arbitrary user (docker-library/wordpress#351)
@uuf6429
Copy link

uuf6429 commented Dec 4, 2018

Not sure why, but ever since this change I have to run this otherwise various WP operations fail (eg; uploading a new plugin requires ftp access, cannot create subdirections inside wp-content/uploads):

$ docker exec -t wordpress_1 chown www-data -R wp-content

Looking back, this problem makes sense since I have some stuff bind-mounted inside wp-contents presumably causing this directory to be created by root. I don't know how this change affected it though.

autophagy pushed a commit to crate/official-images that referenced this pull request Dec 12, 2018
- `ghost`: 2.6.2, more arches (thanks to nodejs/docker-node#921)
- `joomla`: 3.9.1
- `matomo`: php-apcu to 5.1.14 (matomo-org/docker#125)
- `openjdk`: `7u181-2.6.14-2~deb8u1`
- `php`: fix arbitrary user permissions (docker-library/php#755)
- `postgres`: `dpkg-divert` config file for correctness (docker-library/postgres#529)
- `redis`: 5.0.2
- `wordpress`: add `--no-overwrite-dir` for arbitrary user (docker-library/wordpress#351)
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

Successfully merging this pull request may close these issues.

3 participants