Emma Rizzi
06/15/2021, 8:04 AMKevin Kho
06/15/2021, 1:58 PMEmma Rizzi
06/15/2021, 2:02 PMKevin Kho
06/15/2021, 2:04 PMEmma Rizzi
06/15/2021, 2:05 PMKevin Kho
06/15/2021, 2:51 PMEmma Rizzi
06/15/2021, 3:03 PMKevin Kho
06/15/2021, 3:05 PMEmma Rizzi
06/16/2021, 9:39 AMdocker login
on the instance hosting Prefect, the pull worked, I'm almost there!
Now the pull seems more problematic, according to AWS doc I sent, it requires only 2 env vars to pass "when starting the agent". I followed the instruction to ssh to the instance, add vars to ecs.config, I tried to add the vars to RunCongif env vars, and also to the agent when starting it (with --env option)
Each time I got this error on AWS console :
CannotPullContainerError: inspect image has been retried 1 time(s): failed to resolve ref "<http://nexus-release.XXX/multitask_container:2021-06-16t08-00-50-057792-00-00|nexus-release.XXX/multitask_container:2021-06-16t08-00-50-057792-00-00>": unexpected status code [manifests 2021-06-16t08-00-50-057792-00-00]:...
As I can pull the image locally, I guess the problem comes from the authentification. I tried looking into Prefect code to see how the tasks are launched.
Another doc : https://docs.aws.amazon.com/AmazonECS/latest/developerguide/private-auth.html says to give private registry logins to the task definition
I see in the code here that the default container definition is created with only "image", while boto doc indicates we can also provide private registry credentials.
I believe this is the only thing missing to run tasks with private imagesKevin Kho
06/16/2021, 1:43 PMEmma Rizzi
06/16/2021, 1:45 PMdocker login
on the instance hosting Prefect and give a task_definition following this doc to my ECS Agent 🙂Kevin Kho
06/16/2021, 1:46 PMEmma Rizzi
06/18/2021, 7:47 AM