maxking / maxking/docker-mailman

Drop Root in Dockerfile for Security + Offer to Contribute Helm Chart

Open
#761 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
278
Forks
121
PR merge metrics
No merged PRs in 30d

Description

Hi there,

I'm currently building a Helm chart to run Mailman in Kubernetes, and I have everything working well. I'd love to contribute it back if there's interest.

One major issue I noticed is that the container runs as root by default. For better security, I propose splitting the current docker-entrypoint.sh into two stages:

A docker-root-setup.sh script that runs as root to handle setup tasks (e.g., writing config files).

Then switch to USER 100 and run a modified docker-entrypoint.sh as a non-root user (e.g., mailman).

This approach aligns with container security best practices and would make the image safer to use in production environments.

If you're open to the idea, I’d be happy to help implement this. I can also share the Helm chart I'm building to help others deploy Mailman more easily on Kubernetes.

Let me know your thoughts.

Thanks,
Tim

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the Dockerfile and current docker-entrypoint.sh to identify setup steps and how the container user is selected. Check the proposed root setup and non-root runtime flow against the existing image behavior, then verify the container runs successfully as UID 100 and document or share the Helm chart contribution.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, helm, kubernetes, shell
Domain
devops, infrastructure, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.