# Stuck @ CHOWN for /var/www/discourse **URL:** \ **Category:** Self-hosting\ **Created:** [2017 年11 月 15 日 23:16 UTC](https://meta.discourse.org/t/stuck-chown-for-var-www-discourse/74138 "2017-11-15T23:16:48Z")\ **Posts on this page:** 1\ **Showing post:** 14
作者： ![dnsmichi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dnsmichi/32/379505_2.png) [@dnsmichi](https://meta.discourse.org/u/dnsmichi)\ 发布日期： [2018 年5 月 30 日 09:01 UTC](https://meta.discourse.org/t/stuck-chown-for-var-www-discourse/74138/14 "2018-05-30T09:01:39Z")
Maybe could this be put into the native application template? I haven’t rebuilt the app on disk for a while now, since the upgrade via web admin console works like a charm. Upgrading in the docker container works different to the shell rebuild as far as I would guess for now. git pulled plenty of changes. ```plaintext 1392 files changed, 63951 insertions(+), 41658 deletions(-) ``` I don’t have exact times, but I’d say 10 minutes at least where the Docker container was just idle with chown (did a docker exec to inspect what it was doing). System here is running with limited IOPs on a hosting platform. One could also install `parallel` or alter the way find executes chown in multiple processes, e.g. per directory. Would such make sense for a PR? --- _[View the full topic](https://meta.discourse.org/t/stuck-chown-for-var-www-discourse/74138)._