Jim Nisivoccia

10/27/2021, 11:57 PM
Hi everyone, I'm trying to switch my dagit run launcher to use the DockerRunLauncher as opposed to the DefaultRunLauncher, and I am able to pull the proper image for the process run. However, when it goes to start the container for the process, the container is never created and it hangs in "starting" state. Attached is a screenshot of the engine_event below. Has anyone run into this issue before and know some possible solutions? Are there logs that the RunLauncher writes to?


10/28/2021, 12:09 AM
Hi Jim - usually there will be a clue if you call ‘docker logs <container Id>’ using the id from the event log

Jim Nisivoccia

10/28/2021, 12:21 AM
Thank you @daniel! After doing this we found the container was hanging due to a python process we were running in the same container.
:condagster: 1