Allow chown to fail so files can be managed via docker configs and secrets

Intentionally allow chown to fail with exit status 0. Docker swarm 'secrets'
and 'configs' intentionally mount their managed files as read-only within a docker
container. This action will cause the two chown commands to fail with an exit status of
1. That failure in return creates a "container boot loop" within the s6-overlay
'cont-init.d' startup stage when any docker secrets or configs are used to manage files
located within the /i2p/.i2p directory.

docker/rootfs/etc/cont-init.d/00-app-user-map.sh

@@ -19,8 +19,8 @@ echo "$APP_USER:x:$GROUP_ID:" >> /etc/group
 
 # Make sure APP_HOME is editable by the user
 if [[ -n "$APP_HOME" ]] ; then
-    chown -R "$APP_USER" "$APP_HOME"
-    chmod -R u+rw "$APP_HOME"
+    chown -R "$APP_USER" "$APP_HOME" || true
+    chmod -R u+rw "$APP_HOME" || true
 fi
 
 # vim:ft=sh:ts=4:sw=4:et:sts=4