Issues with custom nginx.conf

[stixes]

My setup required some tuning of the nginx.conf file, so I decided to volumemap it. This break the startup script during the initial sed execution.

i.e. -v ./nginx.conf:/etc/nginx/nginx.conf

the mapped nginx.conf is a docker cp from the running container.

I run using docker-compose, so here is the output:

docker-compose up nextcloud
nextclouddb is up-to-date
Recreating ubuntu_nextcloud_1
Attaching to ubuntu_nextcloud_1
nextcloud_1      | Updating permissions...
nextcloud_1      | sed: can't move '/etc/nginx/nginx.confJaKgmH' to '/etc/nginx/nginx.conf': Resource busy
nextcloud_1      | Updating permissions in /nextcloud...
nextcloud_1      | Permissions in /data are correct.
nextcloud_1      | Permissions in /config are correct.
nextcloud_1      | Permissions in /apps2 are correct.
nextcloud_1      | Updating permissions in /etc/nginx...
nextcloud_1      | Updating permissions in /etc/php7...
nextcloud_1      | Updating permissions in /var/log...
nextcloud_1      | Updating permissions in /var/lib/nginx...
nextcloud_1      | Updating permissions in /tmp...
nextcloud_1      | Updating permissions in /etc/s6.d...
nextcloud_1      | Done updating permissions.
nextcloud_1      | /usr/local/bin/occ: line 2: can't open MEMORY_LIMIT: no such file
nextcloud_1      | Trying ownCloud upgrade again to work around ownCloud upgrade bug...
nextcloud_1      | /usr/local/bin/occ: line 2: can't open MEMORY_LIMIT: no such file
ubuntu_nextcloud_1 exited with code 1

My workaround is mapping all of the /etc/nginx , which works fine for some reason.

Let me know if you need help reproducing. Another solution could be to allow the sed command to fail silently, since it's really only used on the initial run of the container.