Those errors should be logged (because they aren't supposed to happen and probably mean that something is wrong somewhere), but we can't do anything about them, since they happen in a goroutine. If someone experiences weird disconnections, at least they might get some hint in the logs about what's really happening.

The goroutine could use a chan argument and send the error back through the channel, but I don't believe that it would be useful here, and it would require a much bigger refactoring. And then again, even if we knew about that error—we couldn't do anything about it. "We were feeding some data to the container's input, and something went wrong." We can't even bubble up the error to the API since this happens in hijack mode (as far as I understand).