Jonas Stoehr

Hi Michael, today I have had some more spare time on my hands. First of all, thank you so much for going into depth with all of this -- when...

@KittlitzMichael Quick update: I just now wanted to start working on the config over at `terraform-provider-rancher2`. While I understood the basic structure of the `node_template*.go` and `structure_node*.go` files, I could...

@KittlitzMichael Given that this is an upstream problem and we were able to work around the problems in today's session, would you be ok with closing this as out-of-scope?

Just FYI: The title is a little misleading, as this happens with Boost.ASIO 1.74, regardless of the platform. I've already [tried to fix this](https://github.com/elsid/resource_pool/compare/master...JonasProgrammer:bug/boost_174_compat), but in the end I failed...

> Looks like I'm a little bit out of sync with Boost.Asio changes. It looks like there are two Executor concepts - Networking TS Executor and Executors TS Executor. And...

I'm not entirely sure everything is fixed, given the fact that we only recently introduced a flag to wait on server creation so outside orchestration does not run in loops,...

Hi, the exit status comes from the commands run by `docker-machine` to provision an already existing server, i.e. the driver has nothing to do with this. Can you try runnning...

Very strange indeed. Can you perhaps try `docker-machine ssh` after the server was created? You don't actually need to wait for the provisioning process to fail, just don't kill it...

Thanks for the observation @mrjackv. Despite maintaining the driver I run mostly on Hetzner metal, so I don't always have an insight as to what is currently happening in the...

Can you try and SSH into the machine after creation to see, whether the docker daemon is actually running (`systemctl status docker.service`) or something alike? Other than that, do you...