https://prefect.io logo
Join Slack
Powered by
Hi :wave: When trying to run a Flow on ECS Fargate...
# ask-community
y
Hi šŸ‘‹ When trying to run a Flow on ECS Fargate I get the error: Submission failed. KeyError: ā€œNo class found for dispatch key ā€˜ecs-taskā€™ in registry for type ā€˜Blockā€™.ā€ The whole setup here is an ECS Task running as a work pool and listens to new Runs. The Task was started with the command ā€œprefect worker start --pool test-poolā€ Then I defined a new deployment with this configuration:
Copy code
prefect deployment build jobs/test1/test1.py:test1 \
--name test1 \
--output jobs/test1/deployment \
--storage-block github/yuvital-prefect-github \
--pool test-pool \
--infra-block ecs-task/ecs-test-block
Meaning when the Work Pool Task poll for a new flow to run, it should also create a new ECS Task for that flow run. Looking at the logs I can see that the work pool do get the new flow to run, but fails with: Submission failed. KeyError: ā€œNo class found for dispatch key ā€˜ecs-taskā€™ in registry for type ā€˜Blockā€™.ā€
z
Sounds like 
prefect-aws
isnā€™t installed in your workerā€™s environment ā€” but note that workers are meant to be used with the 
ECSWorker
not the 
ECSTask
block
i.e youā€™d want a work pool of type 
ecs
rather than 
prefect-agent
y
Yes
This this the Task definition of the work pool:
Copy code
{
  "taskDefinitionArn": "arn:aws:ecs:eu-central-1:759317626178:task-definition/agent-task:8",
  "containerDefinitions": [
    {
      "name": "agent-task",
      "image": "prefecthq/prefect:2-python3.10",
      "cpu": 0,
      "portMappings": [
        {
          "name": "agent-task-80-tcp",
          "containerPort": 80,
          "hostPort": 80,
          "protocol": "tcp",
          "appProtocol": "http"
        }
      ],
      "essential": true,
      "command": [
        "prefect",
        "worker",
        "start",
        "--pool",
        "test-pool"
      ],
      "environment": [
        {
          "name": "PREFECT_API_KEY",
          "value": ""
        },
        {
          "name": "PREFECT_API_URL",
          "value": ""
        },
        {
          "name": "EXTRA_PIP_PACKAGES",
          "value": "prefect-aws s3fs"
        }
      ],
      "environmentFiles": [],
      "mountPoints": [],
      "volumesFrom": [],
      "ulimits": [],
      "logConfiguration": {
        "logDriver": "awslogs",
        "options": {
          "awslogs-create-group": "true",
          "awslogs-group": "/ecs/agent-task",
          "awslogs-region": "eu-central-1",
          "awslogs-stream-prefix": "ecs"
        }
      }
    }
  ],
  "family": "agent-task",
  "executionRoleArn": "arn:aws:iam::759317626178:role/ecsTaskExecutionRole",
  "networkMode": "awsvpc",
  "revision": 8,
  "volumes": [],
  "status": "ACTIVE",
  "requiresAttributes": [
    {
      "name": "com.amazonaws.ecs.capability.logging-driver.awslogs"
    },
    {
      "name": "ecs.capability.execution-role-awslogs"
    },
    {
      "name": "com.amazonaws.ecs.capability.docker-remote-api.1.19"
    },
    {
      "name": "com.amazonaws.ecs.capability.docker-remote-api.1.18"
    },
    {
      "name": "ecs.capability.task-eni"
    },
    {
      "name": "com.amazonaws.ecs.capability.docker-remote-api.1.29"
    }
  ],
  "placementConstraints": [],
  "compatibilities": [
    "EC2",
    "FARGATE"
  ],
  "requiresCompatibilities": [
    "FARGATE"
  ],
  "cpu": "1024",
  "memory": "3072",
  "runtimePlatform": {
    "cpuArchitecture": "X86_64",
    "operatingSystemFamily": "LINUX"
  },
  "registeredAt": "2023-04-26T17:33:57.713Z",
  "registeredBy": "arn:aws:iam::759317626178:root",
  "tags": []
}
z
I donā€™t think ECS respects 
EXTRA_PIP_PACKAGES
because it bypasses our entrypoint
y
Let me understand because I am little bit confused (-:
Iā€™ve created a new work pool like so:
z
I think if you add 
/opt/prefect/entrypoint.sh
at the start of your commands itā€™ll install 
prefect-aws
like you want
y
It runs nice on ECS and listens to new Runs
z
I see ā€” I donā€™t think you can set an infrastructure block when using non-agent work pool types (cc @alex)
y
How should I define a deployment so that it will be picked up by this worker pool?
Ah so itā€™s not possible to create a new ECS Task for each Run?
Meaning when the work pool task polled for a new flow, it should create a new ECS Task.
z
We do create a new ECS task for each run
Thatā€™s how the ECS worker functions
y
Ok, so what I am defining wrong here?
z
Workers donā€™t use infrastructure blocks in the same way that agents do
The work pool defines the infrastructure instead
y
ok, so instead of:
Copy code
prefect deployment build jobs/test1/test1.py:test1 \
--name test1 \
--output jobs/test1/deployment \
--storage-block github/yuvital-prefect-github \
--pool test-pool \
--infra-block ecs-task/ecs-test-block
I should do:
Copy code
prefect deployment build jobs/test1/test1.py:test1 \
--name test1 \
--output jobs/test1/deployment \
--storage-block github/yuvital-prefect-github \
--pool test-pool
(removing the infra from the deployment?)
a
To create a deployment in an 
ecs
work pool, youā€™ll want to use the new Prefect Projects functionality. Following the project tutorial is a good way to get started: https://docs.prefect.io/latest/tutorials/projects/
y
ok got it, and following this method, when the worker pool get a new Run, it will create a new ECS Task for it?
a
Yes, the ECS worker will create a new ECS for each run. Looking at your original error, Iā€™m surprised you got that error for this deployment because workers should not execute flow runs from deployments with a storage block. Do you have any other agents polling this work pool by any chance?
y
No. Iā€™ve checked. Nobody else is polling this work pool.
And also looking at the logs of the work pool:
Like youā€™ve said:
a
Gotcha, thatā€™s a bug. It shouldnā€™t have executed that flow run. Would you please submit an issue for this?
y
Sure Iā€™ll try. I am still trying to wrap my head around all the moving parts.
17 Views
Open in Slack
PreviousNext
Powered by