Hi @iainsproat, I’ve removed all health checks and dependency checks. Snip of sections of the docker output below. Thank you!
postgres_1 |
postgres_1 | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres_1 |
postgres_1 | 2023-10-10 11:10:22.331 UTC [1] FATAL: database files are incompatible with server
postgres_1 | 2023-10-10 11:10:22.331 UTC [1] DETAIL: The data directory was initialized by PostgreSQL version 13, which is not compatible with this version 14.5.
redis_1 | 1:C 10 Oct 2023 11:10:22.710 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 10 Oct 2023 11:10:22.710 # Redis version=6.0.20, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 10 Oct 2023 11:10:22.711 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
redis_1 | 1:M 10 Oct 2023 11:10:22.713 * Running mode=standalone, port=6379.
redis_1 | 1:M 10 Oct 2023 11:10:22.713 # Server initialized
redis_1 | 1:M 10 Oct 2023 11:10:22.713 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
redis_1 | 1:M 10 Oct 2023 11:10:22.714 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo madvise > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled (set to 'madvise' or 'never').
redis_1 | 1:M 10 Oct 2023 11:10:22.720 * Loading RDB produced by version 6.0.20
redis_1 | 1:M 10 Oct 2023 11:10:22.721 * RDB age 4 seconds
redis_1 | 1:M 10 Oct 2023 11:10:22.721 * RDB memory usage when created 0.77 Mb
redis_1 | 1:M 10 Oct 2023 11:10:22.721 * DB loaded from disk: 0.001 seconds
redis_1 | 1:M 10 Oct 2023 11:10:22.722 * Ready to accept connections
preview-service_1 | {"level":"info","time":"2023-10-10T11:09:06.142Z","component":"preview-service","component":"preview-service/server","msg":"Listening on port 3001"}
preview-service_1 | {"level":"info","time":"2023-10-10T11:09:06.144Z","component":"preview-service","msg":"📸 Started Preview Service"}
preview-service_1 | {"level":"error","time":"2023-10-10T11:09:06.183Z","component":"preview-service","err":{"type":"Error","message":"getaddrinfo ENOTFOUND postgres","stack":"Error: getaddrinfo ENOTFOUND postgres\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)","errno":-3008,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"postgres"},"msg":"Error executing task"}
speckle-frontend_1 | {"time_local":"10/Oct/2023:11:10:41 +0000","remote_addr":"10.8.158.87","remote_user":"","request":"GET /graphql HTTP/1.1","status": "502","body_bytes_sent":"982","request_time":"0.000","http_referrer":"","http_user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36"}
speckle-frontend_1 | 2023/10/10 11:10:41 [error] 33#33: *2 connect() failed (111: Connection refused) while connecting to upstream, client: 10.8.158.87, server: , request: "GET /graphql HTTP/1.1", upstream: "http://172.22.0.3:3000/graphql", host: "speckle-test.ramboll.com"
webhook-service_1 | {"level":"error","time":"2023-10-10T11:10:43.592Z","component":"webhook-service","err":{"type":"Error","message":"getaddrinfo ENOTFOUND postgres","stack":"Error: getaddrinfo ENOTFOUND postgres\n at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:107:26)","errno":-3008,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"postgres"},"msg":"Error executing task"}