## Summary (Summarize the bug encountered concisely) ## Steps to reproduce (How one can reproduce the issue - this is very important) ## What is the current bug behavior? (What actuallstandard_init_linux.go:219: exec user process caused: permission denied postgres_image_1 | postgres_image_1 | PostgreSQL Database directory happens) ## What is the expected correct behavior? (What you should see instead) ## Relevant logs and/or screenshots (Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.) ## Possible fixes (If you can, link to the line of code that might be responsible for the problem) ## Defintion of Done - [ ] Bug has been identified and corrected within the containerars to contain a database; Skipping initialization postgres_image_1 | postgres_image_1 | 2021-01-26 23:00:39.102 UTC [1] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit postgres_image_1 | 2021-01-26 23:00:39.104 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 postgres_image_1 | 2021-01-26 23:00:39.104 UTC [1] LOG: listening on IPv6 address "::", port 5432 postgres_image_1 | 2021-01-26 23:00:39.108 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" postgres_image_1 | 2021-01-26 23:00:39.117 UTC [27] LOG: database system was shut down at 2021-01-26 23:00:33 UTC postgres_image_1 | 2021-01-26 23:00:39.124 UTC [1] LOG: database system is ready to accept connections perimeter9-migration exited with code 1