Replies: 2 comments 5 replies
-
|
hi @NathanAP - thank you for opening the discussion can you share which version of prefect is in your image? I know you're using for example, right now I have » docker run prefecthq/prefect:3.0-python3.12 -- prefect version
Version: 3.0.10
API version: 0.8.4
Python version: 3.12.7
Git commit: 3aa2d893
Built: Tue, Oct 15, 2024 1:31 PM
OS/Arch: linux/aarch64
Profile: ephemeral
Server type: ephemeral
Pydantic version: 2.9.2
Server:
Database: sqlite
SQLite version: 3.40.1also, what is in your |
Beta Was this translation helpful? Give feedback.
-
|
Hello, thanks for answering! I got the exact same result as yours when checking for prefect in docker. This is my from dotenv import load_dotenv
from prefect import serve # type: ignore
load_dotenv()
if __name__ == "__main__":
import flows as Flows
postgresql_flow = Flows.backup_postgres_flow.to_deployment(
name="backup-postgres",
cron="0 4 * * *",
)
qdrant_flow = Flows.backup_qdrant_flow.to_deployment(
name="backup-qdrant",
cron="0 4 * * *",
)
data_folder_flow = Flows.backup_data_folder_flow.to_deployment(
name="backup-data-folder",
cron="0 4 * * *",
)
shared_folder_flow = Flows.backup_shared_folder_flow.to_deployment(
name="backup-shared-folder",
cron="0 4 * * *",
)
serve(
postgresql_flow,
qdrant_flow,
data_folder_flow,
shared_folder_flow,
)Is there a better / easier way to archieve this same result? |
Beta Was this translation helpful? Give feedback.
-
|
Just to be sure we are in the same page: I'm trying to do something like this: |
Beta Was this translation helpful? Give feedback.
-
|
Hey @NathanAP! It looks like you're running your server and serving flows in the same container. It might be easier to run your server in one container and your served flows in another. I haven't tested this, but I think a Docker compose file like this could work: version: '3'
services:
prefect:
tty: true
build:
context: ./prefect_scheduler
dockerfile: Dockerfile
container_name: prefect
volumes:
- ./data:/opt/prefect/data
- ./prefect_scheduler:/opt/prefect/prefect_scheduler
- ./shared:/opt/prefect/shared
environment:
- PREFECT_SERVER_API_HOST=0.0.0.0
- PREFECT_API_DATABASE_CONNECTION_URL=****
- PREFECT_API_DATABASE_MIGRATE_ON_START=True
ports:
- "4200:4200"
networks:
- my-network
served_flows:
image: your-served-flows-image
container_name: served_flows
environment:
- PREFECT_API_URL=http://prefect:4200/api
networks:
- my-network
networks:
my-network:
driver: bridgeThe key part is setting the |
Beta Was this translation helpful? Give feedback.
-
|
To be honest this error only occurs in a production stage (I'm trying on GCP). When I make I will try to make a separate container to serve all of the flows to the |
Beta Was this translation helpful? Give feedback.
-
|
Was running into this same issue. It was probably due to the prefact-server service being started while the server was still down, when the worker started. A quick and dirty fix that did the job for me was to add a couple of seconds of sleep before starting the worker.
|
Beta Was this translation helpful? Give feedback.
-
|
hi @serveri24h - these docs might be useful to you |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm trying to use Prefect in a staging level of my project, but when I start my Docker I get the following logs:
This is my
docker-compose:and this is my Dockerfile:
My
run.shis this:I'm not sure what could be causing it because other containers works fine and this is the only one refusing connections.
Beta Was this translation helpful? Give feedback.
All reactions