mirror of
https://github.com/mjl-/mox.git
synced 2025-07-12 18:24:35 +03:00
replace use of docker registry docker.io (hub.docker.com) with self-hosted r.xmox.nl
when setting up the docker organization account for mox it already felt off. depending on such a party to serve binaries didn't feel great to begin with. after clarifying online discussions of docker's vague announcement of removing free team organizations it was clearly time to move off hub.docker.com. best to self-host. r.xmox.nl is hosted with the new github.com/mjl-/vex. pinging issue #3
This commit is contained in:
11
README.md
11
README.md
@ -60,12 +60,11 @@ Verify you have a working mox binary:
|
||||
|
||||
Note: Mox only compiles for/works on unix systems, not on Plan 9 or Windows.
|
||||
|
||||
You can also run mox with docker image "docker.io/moxmail/mox", with tags like
|
||||
"latest", "0.0.1" and "0.0.1-go1.20.1-alpine3.17.2", see
|
||||
https://hub.docker.com/r/moxmail/mox. See docker-compose.yml in this
|
||||
repository for instructions on starting. You must run docker with host
|
||||
networking, because mox needs to find your actual public IP's and get the
|
||||
remote IPs for incoming connections, not a local/internal NAT IP.
|
||||
You can also run mox with docker image `r.xmox.nl/mox`, with tags like `v0.0.1`
|
||||
and `v0.0.1-go1.20.1-alpine3.17.2`, see https://r.xmox.nl/repo/mox/. See
|
||||
docker-compose.yml in this repository for instructions on starting. You must run
|
||||
docker with host networking, because mox needs to find your actual public IP's
|
||||
and get the remote IPs for incoming connections, not a local/internal NAT IP.
|
||||
|
||||
|
||||
# Quickstart
|
||||
|
Reference in New Issue
Block a user