external/mailinabox
1
0
Fork 0
mirror of https://github.com/mail-in-a-box/mailinabox.git synced 2026-03-05 15:57:23 +01:00
Code Issues Releases Wiki Activity

docker: re-run the start script on the container's first run because it won't know its hostname or IP address until then

Browse Source
This commit is contained in:
Joshua Tauberer
2014-05-02 14:23:56 -04:00
parent 3fdcbe542f
commit 189dd6000e
3 changed files with 31 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
Dockerfile
View File

@@ -5,10 +5,11 @@
# To build the image:
# sudo docker.io build -t box .
# To run a container for testing (with a command prompt and no publicly exposed ports):
# sudo docker.io run -i -t -P box
# Run your container the first time with an interactive console so you can
# create your first mail account.
# sudo docker.io run -i -t box
# Or to run in the background and expose all of the ports so that the *host* acts as a Mail-in-a-Box:
# Then run it in the background and expose all of the ports so that the *host* acts as a Mail-in-a-Box:
# (the SSH port is only available locally, but other ports are exposed publicly and must be available
# otherwise the container won't start)
# sudo docker.io run -d -p 22 -p 25:25 -p 53:53/udp -p 443:443 -p 587:587 -p 993:993 box
@@ -18,9 +19,10 @@ MAINTAINER Joshua Tauberer (http://razor.occams.info)
# We can't know these values ahead of time, so set them to something
# obviously local. The start.sh script will need to be run again once
# these values are known.
# these values are known. We use the IP address here as a flag that
# the configuration is incomplete.
ENV PUBLIC_HOSTNAME box.local
ENV PUBLIC_IP 127.0.123.123
ENV PUBLIC_IP 192.168.200.1
# Docker-specific Mail-in-a-Box configuration.
ENV DISABLE_FIREWALL 1