Open LittleAmara opened 7 months ago
:thinking: not sure, that looks unusual... a few things you could try is setup an env_logger
and set the environment RUST_LOG=bollard=trace
to see whether a request was made and it's waiting on something in your program. Also, put your docker daemon into debug mode and read the docker daemon logs, to check if a connection was made.
Hey, nothing that can help came out of the logs of both bollard and docker.
What I really do not understand is that calling whatever *_images
functions does unlock the loop but calling info
does not for example...
I had another look and tried executing the code -- it looks to me like the tokio_scheduler
crate isn't scheduling another run when the docker client calls execute. It doesn't look like it hangs at that point though... Perhaps it's worth asking with the tokio_scheduler maintainer for any ideas.
Heyo,
In the code below I am trying to check if there is a container up on the machine, if not then I will create one and start it (which I did not include is the snippet as it is useless here) and I think I found an issue.
It seems that
create_container
hangs indefinitely in the tokio task. One way to fix it is to call another function likelist_images
but I am almost sure that this is not intended.