Did you see automatic increase of the disk usage right after bundle install to newer version ?   Could you pls share before and after upgrade snapshot on the same device to get clear understanding ?    For now try to clean up docker layers on local registry using below ioxclient command and then install again. $ ioxclient layer delete ... View more

Few things to change from your end. We identified the root cause in overlayfs and it will be addressed in next IR829 release. In the intermediate term, here is the workaround.   1. Use linux development machine to rebuild iox app package.  2. Setup package.yaml's rootfs attribute value as "app.ext2" and add user attribute in startup section. Here is the final version. descriptor-schema-version: "2.7" info: name: postgre_829 version: latest app: cpuarch: x86_64 env: PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin resources: network: - interface-name: eth0 ports: tcp: - "5432" profile: c1.large startup: rootfs: app.ext2 target: ["/usr/lib/postgresql/9.3/bin/postgres", "-D", "/var/lib/postgresql/9.3/main", "-c", "config_file=/etc/postgresql/9.3/main/postgresql.conf"] user: postgres type: docker 3. Repackage iox app using this command. -p ext2 option will not take overlayfs path and instead mount as ext2 fs. $ ioxclient docker package -p ext2 <docker_image> <dir path containing package.yaml> 4. Upload/activate/start the app. Make sure to Activate the app in debug mode, so that container is up and running even if target process is down. 5. At this point, i still see postgres exiting due to this error. root@IR800-GOS-1:/# cat /data/logs/watchDog.log 2019-07-25 02:11:42.161 UTC [152] FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied App postgres_ext2 completed with exit code: 1 APP END TIME:1564020702 Time taken by App : 0 minutes and 1 seconds. Main process died, so dropping the container in to shell for debugging 6. Get inside application console using command $ ioxclient app console <appname> 7. Now try to manually start the app as postgres user and i could see the postgres getting started fine. Try to see if ssl-cert-snakeoil.key permission needs to be changed for fixing the error in step 5. root@IR800-GOS-1:/# su postgres postgres@IR800-GOS-1:/$ postgres@IR800-GOS-1:/$ whoami postgres postgres@IR800-GOS-1:/$ /usr/lib/postgresql/9.3/bin/postgres -D /var/lib/postgresql/9.3/main -c config_file=/etc/postgresql/9.3/main/postgresql.conf 2019-07-25 02:12:19.354 UTC [161] LOG: database system was interrupted; last known up at 2019-07-12 18:34:46 UTC 2019-07-25 02:12:20.446 UTC [161] LOG: database system was not properly shut down; automatic recovery in progress 2019-07-25 02:12:20.451 UTC [161] LOG: redo starts at 0/1784C28 2019-07-25 02:12:20.453 UTC [161] LOG: record with zero length at 0/1784C68 2019-07-25 02:12:20.453 UTC [161] LOG: redo done at 0/1784C28 2019-07-25 02:12:20.454 UTC [161] LOG: last completed transaction was at log time 2019-07-12 18:34:46.275325+00 2019-07-25 02:12:20.480 UTC [161] LOG: MultiXact member wraparound protections are now enabled 2019-07-25 02:12:20.512 UTC [160] LOG: database system is ready to accept connections 2019-07-25 02:12:20.508 UTC [165] LOG: autovacuum launcher started Let me know if you are not able to get this still working.   ... View more

I could recreate the issue #1. But with the workaround you suggested to execute postgres process as user "postgres, i could get the process up and running and access the "docker" database.   Is there any particular operation you are trying which lead to the error ?   [283] FATAL: could not open lock file "postmaster.pid": Permission denied   ... View more

Could you pls share your dockerfile contents, package.yaml OR just app pkg.tar? Also which version of IOx are you using in IR829 ? Also generate techsupport snapshot from Local Manager System Troubleshoot tab and share the same. ... View more