The go API bindings have been tested with a large number of simultaneous create/start/destroys, so I believe the upstream API thread-safety work must have fixed this at least upstream.
The go API bindings have been tested with a large number of simultaneous create/ start/destroys, so I believe the upstream API thread-safety work must have fixed this at least upstream.