Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Unfortunately not.
Well crap. Do you have no ipv6 address now in
ip addr
?Guess I gave Docker too much benefit of the doubt and assumed it should failover to v4 once v6 was disabled. Bad assumption on my part.
Could it be a DNS problem? If you
dig registry-1.docker.io +short
does it return an ipv4 or v6 address?It looks like there have been sporadic reports of problems from people since last year.
Try adding
{"ipv6": false}
to your/etc/docker/daemon.json
file (create it if it doesnt exist), then restart docker withsudo systemctl restart docker
- this forces docker to use IPv4 only.This flag seems to only disable ipv6 on the default Docker bridge network, not daemon-wide. At least per this discussion.
Just comparing it by eye, there's no change.
But if I ping it
It's in the dnsutils package.