Maxime Petazzoni

So, giving more thoughts to this, the main issue with the proposal above is that it's not a graceful restart at all. At step 4, the whole stack is down....

It's hard to say what is correct here. I feel like their could be different answers based on what the nature of the dependency is.

Hmm, I'm not able to reproduce this problem. Same Maestro version, same Docker version, same environment file. The only difference is that I'm using Python 3.7. Would you be able...

You're most likely still executing with Python 2.x. When a pip package installs a binary, it embeds the path to the Python executor: ``` $ head -n1 `which maestro` #!/opt/boxen/homebrew/Cellar/python/3.7.3/bin/python3.7...

So maybe run `pip3 install --upgrade docker-py` and retry?

If that fixes it, it might mean I have to set a minimum version requirement for `docker-py` in my `requirements.txt` file.

I can definitely reproduce the problem. It seems to be depending on the target host though, not necessarily on the Maestro/Python versions. Investigating...

Hmm, I concerned this is going to be hard to fix. Here are my findings. As you mentioned, the problem comes from `_validate_ssh_process()`, which waits until some output comes from...

If one of you has some time, can you try with a hacked version of `bgtunnel.py` that doesn't add the `-T` option to the SSH command args?

Thanks for the workaround @corvis. Unfortunately there isn't much Maestro can do here to help. https://github.com/jmagnusson/bgtunnel/issues/7 tracks the issue already on bgtunnel's side.