docs: Add Matrix links, Docker changes #782
No reviewers
Aranjedeath
nex
Labels
No labels
Blocked
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!782
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "jade/docker-warning"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is the docker DNS performance issue documented anywhere? It definitely needs to be prominent because docker DNS is a federation killer, hardly exaggerating
I wasn't fully aware there was a DNS performance with Docker, so I don't think it's documented. I haven't been having any major issues with my homeserver, although it does run on Podman - not sure how different the DNS setup is there.
Not sure if it's all green in podland, but docker's DNS causing federation performance issues is a well known phenomenon even outside of matrix. IIRC it was recommended somewhere to pass through /etc/resolv.conf as a bind mount to bypass it but I can't remember where that is
can confirm, recommended quite a number of people deploy an unbound somewhere nearby to solve their docker-dns issues which were preventing federation due to inability to keep up with the dns requests.
Perhaps we should have an entire section for DNS performance because it's something that massively hinders the user experience and a lot of people don't set it up properly
According to docker's docs:
It's possible this only affects people using Docker's embedded resolver by using a non-default network?
Agreeing on the DNS performance section.
Afaik, docker intercepts the DNS requests, or at least it does in compose, to resolve other container names on the docker network. This is where the performance issue comes from, and why manually binding /etc/resolv.conf bypasses the issue
docs: Tone down the docker warningto docs: Add Matrix links, Docker changesI've pushed some new changes, including an explanation of the docker issues as far as I understand them.
Note for later: It's likely that the example Compose files actually trigger Docker's DNS issues, and we should fix them or remove them.
@Jade wrote in #782 (comment):
I still think that having a dedicated page/big section to mentioning general DNS performance issues and workarounds would go further than this, but sounds good in the meantime
looks good, I just think the matrix.to links shouldn't be urlencoded
@ -107,3 +107,3 @@#### Contact<!-- TODO: contact details -->Join our [Matrix room](https://matrix.to/#/%23continuwuity:continuwuity.org) and [space](https://matrix.to/#/%23space:continuwuity.org) to chat with us about the project!https://matrix.to/#/%23continuwuity:continuwuity.org->https://matrix.to/#/#continuwuity:continuwuity.orghttps://matrix.to/#/%23space:continuwuity.org->https://matrix.to/#/#space:continuwuity.org(percent-encoded sigils sometimes freak out the site, for some reason)
d7274a18ab0307238bf8Just for historical purposes, the DNS/docker information and solutions are currently part of Troubleshooting page on our wiki which is how I first found out about the DNS issues and I think moving the changes into the main READ.me will at least help make clear to new users who may not sniff through all the docs.