fix: changed container hostname #50
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
This PR fixes an issue with database backups when the databases are using another container's networking, as is done with tailscale containers (ie, with
network_mode: service:<service_name>syntax).In those instances, the container ID doesn't work as a hostname, since a different container is actually the host traffic is traveling through, so I set it to grab the hostname from the container config instead.
Most of the line changes are formatting changes caused by my editor automatically running black on the file. I can make a more precise change in vim if you prefer, I'd also be happy to make a PR that adds
blackor ruff (by the uv maintainers) to uv/the workflow more generally.