Martin Braun
Martin Braun
I think we should improve the code on our end. I am just pointing out that maybe data should not be logged out to stdout by default.
Its fine. The comment didnt make sense after all. After some digging I found that the issue was not introduced by new code but rather already existed for a while....
transaction_timeout is maybe more what we want for requests? We probably want to undo this after every request is finished. It's important to not break any existing client pooling.
Very important: We should not shoehorn something into NF Compose just because we can. This tickets is here to keep track of ideas and notes on what could be useful....
Posting this here again, as #46462 is closed: I intermittently had this issue as well on a swarm cluster on Hetzner Cloud. Only ever happened once so far. I originally...
It has not happened for a while on our clusters, but I think I remember that it even had a duplicated ID in my case. Could be bad memory, though....
Can you check the output of all nodes from the view of all manager nodes? I remember that part of the cluster was seeing it one way, the other part...
The go-plugin-helpers might not support it after all though? https://github.com/docker/go-plugins-helpers/blob/6eecb7beb65124bb44a23848bb46e98b4f50ae18/volume/api.go#L83
If the label stuff does not work, we could work around it for our usecase by making the label the volume driver sets configurable and just deploy the volume driver...
closing this. we will be going down the route of prefixing.