Open ywangwxd opened 19 hours ago
Hey @ywangwxd,
The fact that the container id is the same leads me to believe that you might still have a stuck pod that is hidden when you run docker ps
but will be shown with the --all
flag.
Try running the full command yourself and check if you can see the pod:
docker ps --quiet --all --filter "name=^/nuclio-nuclio-pth-facebookresearch-sam-vit-h$
Nuclio Version checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of Nuclio.
Issue Description
I encountered this issue while attempting to deploy the Facebook SAM function from docker image for the CVAT project. It hangs after buliding the image. To be specific, it hangs when inspect the container.
Expected Behavior
I would expect the cleanup stage to go well and if it didn't, I could at least disable it.
Deployment Method
Docker
Nuclio Version
1.13
Additional Information
Here is the last piece of logger output when using the --verbose option in the nuctl deploy command. It is strange that initially the container is found, but when I attempt to inspect it, it hangs. I checked the Linux console and found that the container did not exist at all.
Another weird thing is that the container ID 96cde29537ef remains the same for different runs. Shouldn't a container be freshly started for each run?