https://dagster.io/ logo
#ask-community
Title
# ask-community
l

Logan Bonsignore

02/10/2023, 6:48 PM
Hello, i am working on an open source deployment of dagster. When i compose up I get the following error:
Copy code
Resource handler returned message: "Invalid request provided: CreateService error: TaskDefinition can not be blank. (Service: AmazonECS; Status Code: 400; Error Code: InvalidParameterException; Request ID: 6537e8e4-ebc0-4006-abbe-539a8c58aeef; Proxy: null)" (RequestToken: 06013cf9-0073-e0c9-a7a7-806f13632e33, HandlerErrorCode: InvalidRequest)
I saw this issue which mentions a fix, but I am still seeing the error. Any advice here? Thanks
🌈 1
j

johann

02/10/2023, 7:05 PM
what version are you on?
what service is logging that error?
l

Logan Bonsignore

02/10/2023, 7:06 PM
I’m using v1.1.13
Its the UserCodeService that’s logging this error
j

johann

02/10/2023, 7:11 PM
What version of dagster is installed in the user code image?
l

Logan Bonsignore

02/10/2023, 7:12 PM
Its running 1.1.13
j

johann

02/10/2023, 7:13 PM
hmm, that’s odd
just to clarify this is with you deployed to ECS via the provided docker compose?
l

Logan Bonsignore

02/10/2023, 7:13 PM
Yes thats correct
j

johann

02/10/2023, 7:14 PM
And did you make any modifications to the compose files?
l

Logan Bonsignore

02/10/2023, 7:14 PM
Only thing i had to add was some overlays to configure subnets like described here
👍 1
j

johann

02/10/2023, 7:16 PM
Is there a stack trace along with the error
l

Logan Bonsignore

02/10/2023, 7:19 PM
No i do not see one
j

johann

02/10/2023, 7:20 PM
Ah I missed that this comes on the compose up call. The issue you linked arose within Dagster code, but this error is coming up just in the translation from the docker compose to ECS
I’m not aware of any fixes, but could you try this on 1.1.18 (latest) just to confirm?
l

Logan Bonsignore

02/10/2023, 7:21 PM
Okay thanks for looking into it. ill give the latest version a try and report back
j

johann

02/10/2023, 7:27 PM
I’m also curious if the compose up succeeds without the overlays (ignoring if the containers eventually fail bc they aren’t configured)
l

Logan Bonsignore

02/10/2023, 10:24 PM
@johann ran it with dagster 1.1.18 and got the same error
Tried it without the overlays and it worked. But im using the overlays to control my subnets, so it fails later due to incorrect subnets. Do you know of another way to control subnets? Thanks
Copy code
x-aws-cloudformation:
  Resources:
    DagitService:
      Type: 'AWS::ECS::Service'
      Properties:
        NetworkConfiguration:
          AwsvpcConfiguration:
            Subnets:
              - subnet-0364ab18a61e86566
              - subnet-03fb020f50d7dacd8
    DaemonService:
      Type: 'AWS::ECS::Service'
      Properties:
        NetworkConfiguration:
          AwsvpcConfiguration:
            Subnets:
              - subnet-0364ab18a61e86566
              - subnet-03fb020f50d7dacd8
    UserCodeService:
      Type: 'AWS::ECS::Service'
      Properties:
        NetworkConfiguration:
          AwsvpcConfiguration:
            Subnets:
              - subnet-0364ab18a61e86566
              - subnet-03fb020f50d7dacd8
    LoadBalancer:
      Properties:
        Subnets:
          - subnet-0364ab18a61e86566
          - subnet-03fb020f50d7dacd8
Here are my overlays for your reference
j

johann

02/13/2023, 3:07 PM
I’m not familiar with compose overlays unfortunately. On stack overflow it seems like a couple users have hit weird errors like this just by having bad whitespace in their compose file, maybe something to check for
b

Bartek Grasza

02/17/2023, 2:47 PM
@Logan Bonsignore Make sure that both subnets are public
l

Logan Bonsignore

02/17/2023, 5:34 PM
@Bartek Grasza both subnets have a nat gateway on them that allows access to the internet