You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dealing with use cases where dnsdock may not run in the same daemon that it manages and where for some reason event stream may go down and lose data, the changes coming from docker daemon and manually by user are easy to get mixed up and not easy to solve.
I'm suggesting to make container names immutable(docker rename remains the exception) and change it so PATCH request may only change the TTL value and nothing else(or other values can only be changed on containers created with HTTP server). This was always the intention for this method for me.
Because this would be a behaviour breaking change I'm leaving this out here for counter arguments for some time.
I would also release v2.0 so accidental updates should be limited.
The text was updated successfully, but these errors were encountered:
Dealing with use cases where dnsdock may not run in the same daemon that it manages and where for some reason event stream may go down and lose data, the changes coming from docker daemon and manually by user are easy to get mixed up and not easy to solve.
more background in #27
I'm suggesting to make container names immutable(
docker rename
remains the exception) and change it soPATCH
request may only change the TTL value and nothing else(or other values can only be changed on containers created with HTTP server). This was always the intention for this method for me.Because this would be a behaviour breaking change I'm leaving this out here for counter arguments for some time.
I would also release
v2.0
so accidental updates should be limited.The text was updated successfully, but these errors were encountered: