Hi all, I’m having trouble running the hello-world flow based on the tutorial (First Flow). It’s been modified and runs on all my coworkers computers but for some reason, when I run it, I get the

Name or service not known

error message. I confirmed that GraphQL is not running based on the error message on the top right of the prefect UI. Stack trace:

apollo_1    | Checking GraphQL service at <http://graphql:4201/health> ...
apollo_1    | Checking GraphQL service at <http://graphql:4201/health> ...
graphql_1   | 
graphql_1   | Running Alembic migrations...
graphql_1   | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
graphql_1   | INFO  [alembic.runtime.migration] Will assume transactional DDL.
graphql_1   | 
graphql_1   | Could not upgrade the database!
graphql_1   | Error: HTTPConnectionPool(host='hasura', port=3000): Max retries exceeded with url: /v1/query (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x40133ab7d0>: Failed to establish a new connection: [Errno -2] Name or service not known'))
apollo_1    | Checking GraphQL service at <http://graphql:4201/health> ...

Based on the stack trace, it confirms that there is an issue with graphql, I’m just not sure how to dive deeper. I have tried Dagster and initially came across some issues with compatibility with the M1 chip so I created an EC2 instance and tried the prefect first flow tutorial in that one as well. I hit an issue with docker compose not being found so rather than splitting into two separate paths, I’m going to try to focus on getting the first flow tutorial working on my local instance (macos)

Hi @Edward Chen -- Prefect Core does not support arm64 yet but you can checkout the https://github.com/PrefectHQ/server/tree/arm64 branch of Prefect Server and follow the developer instructions at https://github.com/PrefectHQ/server/tree/arm64#running-the-system-as-a-developer and then run the UI container separately. We'll probably be getting those changes tested and merged into a core release in the next few weeks so

prefect server start

works on m1.

Ah perfect, thanks for the quick reply! I’ll look through the links!

It's unfortunately a bit of work to spin up the Server this way, alternatively you could build the Server dockerfile from that branch then change the prefect core docker-compose file to reference your local image.

got it, that sounds like a quicker resolution. I’ll try that, thanks!

Let me know if you run into problems and I may be able to help, still an experimental fix 🙂

I did actually run into an issue, it seems like one of the dependencies (psycopg2-binary) isn’t yet supported for arm64.

#13 7.837 WARNING: Discarding <https://files.pythonhosted.org/packages/77/09/4991fcd9a8f4bea1ee3948e1729fa17c184d25bd10809bacc143626361b9/psycopg2-binary-2.7.4.tar.gz#sha256=de4f88f823037a71ea5ef3c1041d96b8a68d73343133edda684fd42f575bd9d7> (from <https://pypi.org/simple/psycopg2-binary/>). Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.
#13 7.837 ERROR: Could not find a version that satisfies the requirement psycopg2-binary<3.0,>=2.7 (from prefect-server)
#13 7.837 ERROR: No matching distribution found for psycopg2-binary<3.0,>=2.7

Confirmed by doing a

pip install psycopg2-binary

and that hit an error as well. I hit this issue with another package too so I can work on getting prefect working in my EC2 instance, unless you happen to know a quick fix? No worries if you don’t, I understand how much work is involved and I appreciate the quick responses!

Is this while building the docker image?

right right, i decided to go with the latter approach you mentioned and build the image with the intent of changing the docker-compose file

That makes sense--I've only tested the local development way, I was worried there may be some installation issues there. I can look into building the docker image but I may not sort it out today.

No worries! I have an EC2 instance anyways since I’ve been coming across issues where packages aren’t supported yet. The plan is to try again on the EC2 instance but if that doesn’t work, I’ll definitely try using Cloud. Appreciate the quick feedback!