[GitHub] kocolosk opened a new issue #80: Chown in docker-entrypoint.sh is clashing with Kube ConfigMap RO behavior

[GitBox <gi...@apache.org>]

kocolosk opened a new issue #80: Chown in docker-entrypoint.sh is clashing with Kube ConfigMap RO behavior
URL: https://github.com/apache/couchdb-docker/issues/80
 
 
   In kubernetes/kubernetes#58720 the Kubernetes project switched to mounting `configMap` volumes read-only. This was done in part to prevent users getting surprised by any changes they made in those volumes getting overwritten by Kube itself.
   
   While we had anticipated the problem with writing anything into a `configMap` volume back in #50, the entrypoint script still does a blanket chown of all of `/opt/couchdb` (along with some other chmods) which caused breakage with the 1.9.4 release of Kube. See e.g.
   
   kubernetes/charts#4194
   kubernetes/charts#4666
   kubernetes/charts#5438
   
   The workaround implemented in kubernetes/charts#5440 mounts the `configMap` in a temporary location, copies the file into a separate `emptyDir` volume, and then mounts to `default.d`, but this is pretty icky. I'm wondering if we can tweak things upstream here so all that chicanery isn't required.
   
   @wohali what do you think? I've seen some other patches that mask the chmod/chown failures as well, e.g. https://github.com/apache/couchdb-docker/compare/master...hsz-devops:master, but not sure of the best approach here.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services