Hi team. When spinning up the docker containers wi...
# ask-community
n
Hi team. When spinning up the docker containers with
prefect server start
, two of the containers get stuck in a restart loop. Could anyone assist with next steps in fixing these issues below? Error from the container t_hasura_1 :
graphql-engine: error while loading shared libraries: /usr/lib/aarch64-linux-gnu/libpq.so.5: file too short
Error from the container t_graphql_1 :
Error: HTTPConnectionPool(host='hasura', port=3000): Max retries exceeded with url: /v1/query (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x4009e17990>: Failed to establish a new connection: [Errno -2] Name or service not known'))
Hi team. Following up on this question. Can anyone help?
z
I’m not sure our Hasura version supports arm64
n
Do you know what I would do to correct this? Directing the container to read from this location wasn’t an intentional change on my end
z
Hm this is looking a little tricky
What OS are you using?
n
macOS Monterey 12.6.1
z
It looks like you may be able to do
prefect server config
and add a
platform: linux/arm64
annotation then run
docker-compose up
— Docker is a little confusing here https://github.com/docker/cli/issues/1050#issuecomment-899332696
Ah on an M1?
n
yes, but i have other team members who are on an M1 and they haven’t encountered this for some reason
z
Oh interesting
That’s really weird. Running the container on a different platform will be really slow.
I’m not sure I have good advice 😕 you’ll need to find the difference between their setup and yours. Maybe Docker versions? I’d also check what Hasura container tag is being used.
👍 1
n
Issue has been resolved. This error was not due to arm64, but instead corruption of my docker files. Using docker’s clean/purge data option resolved the issue
z
Great! Thanks for reporting back.