£Á°èZ¨Ä…–K§‚«“ô4“ÒÙ´dîfUÙÃÅ WKbyʦ•êŽ…È®FÒ¿ÊÎóCozá¬S@6{Í:›œêZÌ:Š•_%:¢¾¾~;‘Ã~芩ÊǍí`ÔÑ©ú뙵'5I¿fš×WO%ø9¾«¾DK|€ùÍD”Ýs]nHÕ¶êםӼ㞪éUWŸÈË%DÒÕ¬ï‘]/Åcx ‰ï2ß]ä6G[]S£Ôϯrs{úëóµmÒï#UQxo·õÞCe]"±/aÙ&Eã4ú9Jé_ÞåëdãöKë)AÞ ¯¹ægƒÛowЍø^d™ý½ßB7áyMä9ÜÖUã !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! #!/usr/bin/env bash set -e chown -R "$APP_UID:$APP_GID" /home/app groupmod -g "$APP_GID" app usermod -u "$APP_UID" -g "$APP_GID" app # There's something strange with either Docker or the kernel, so that # the 'app' user cannot access its home directory even after a proper # chown/chmod. We work around it like this. mv /home/app /home/app2 cp -dpR /home/app2 /home/app rm -rf /home/app2 if [[ $# -gt 0 ]]; then exec "$@" fi