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
I use dokku/dokku for container management. When I use git push to deploy my server, a new container is created with a Docker-style randomly generated name (eg: optimistic_williams). After about 10 seconds without the server crashing, the new container is renamed to the name of the previous container. This supports zero downtime, but the SumoLogic collector is not updating the name of the new container, which results in its logs not being associated with its new name.
Is there anyway to avoid this?
The text was updated successfully, but these errors were encountered:
currently we don't have way to refresh the container name when it's still running. What you can try is stop and restart container (if possible) and the name should be refreshed.
I use dokku/dokku for container management. When I use
git push
to deploy my server, a new container is created with a Docker-style randomly generated name (eg:optimistic_williams
). After about 10 seconds without the server crashing, the new container is renamed to the name of the previous container. This supports zero downtime, but the SumoLogic collector is not updating the name of the new container, which results in its logs not being associated with its new name.Is there anyway to avoid this?
The text was updated successfully, but these errors were encountered: