aurexs/mailhog repository overview

⁠mailhog-docker

Docker Mailhog

⁠Setup

You need Docker runtime installed, and access to a user that can download, build and run docker images.

• on other platforms⁠

⁠Build (optional for x86 users)

git clone https://github.com/aurexs/docker-mailhog
cd docker-mailhog
docker build -t mailhog:alpine -t mailhog:latest .

⁠Run

⁠After build

docker run --restart always --name mailhog -p 1025:1025 -p 8025:8025 -d mailhog:alpine

⁠From latest on dockerhub

docker run --restart always --name mailhog -p 1025:1025 -p 8025:8025 -d aurexs/mailhog:latest

There are also pre-built versions under cd2team/mailhog with latest tag for rolling release built, tagged and pushed using Github Actions. It's not robustly tested, but the tagging strategy used also means a timestamp release is published to ensure you can pin dependency versions.

The additional {timestamp} version of tags make it easy to maintain history when re-tagging a latest and alpine. If you encounter issues with a latest tag, please try the timestamp from your last successful build, which will share a hash with your last working latest.

⁠Troubleshooting

⁠This isn't intercepting my mail?

• Are you sending emails on the 1025 or 8025 ports?
• Are you using a hostname which resolves to the mailhog docker-container, such as localhost or '127.0.0.1'?
• is the docker service running (does docker ps -a show mailhog Status as "Up {n} Hours|Mins|Secs|Days")

⁠Special Thanks to

• CODESIGN2⁠ - Original work.
• Docker⁠ - for working on the packaging, distribution, runtime.
• GBAMan⁠ - for documenting device-mode extensions for raspberry pi so well.
• Alpine Project⁠ - for making lightweight docker-images that have less moving parts.
• MailHog⁠ - for making the program we run in docker, on alpine, and I combine with device-mode on a raspberry pi zero.
• GitHub & Actions team⁠ - Wonderful humans, making cool tools.
• CrazyMax BuildX⁠ - Without this it would be much harder to supply multi-device-architecture images.