Repository navigation
use central script to create user in all containers #162
Description
instead of adding and setting the openvox/puppet user in each container and hope to hit the smae defaults, why not make it a central implementation?
we could create a base image, or put a script in a repo and used it in all containers.
Base images could look like this: https://github.com/rwaffen/container-base/blob/main/Containerfile.alpine
or usage of a central script could look like this:
FROM docker.io/alpine:3.24 AS prepare
ENV \
OPENVOX_GID=64604 \
OPENVOX_UID=64604 \
OPENVOX_USER_NAME=puppet \
OPENVOX_GROUP_NAME=puppet \
OPENVOX_USER_HOME=/opt/puppetlabs/server/data/puppetserver \
OPENVOX_USER_SHELL=/sbin/nologin
RUN apk update && apk add --no-cache bash curl && \
curl -sL https://raw.githubusercontent.com/rwaffen/container-base/refs/heads/main/prepare.sh | bash -
i think the base container would be the cleanest approach. but thought maybe have an alternative to this.
Activity
miharp commentedon Jun 30, 2026
Could we use
msyncand https://github.com/voxpupuli/container_modulesync_configs with moduleroot/.../create-openvox-user.sh.erb in that config repo, with the canonical UID/GID in config_defaults.yml and any per-repo overrides in each repo's .sync.yml.msyncthen renders and commits the script into each container repo, where the Containerfile COPYs and runs it.I like the base image idea but seems like overkill for this specific user creation issue, my 2 cents :)
rwaffen commentedon Jun 30, 2026
ah yes... msync 🤦 ... that’s an option too. I ramped up all templates lately, so why didn't I come up tih that? :D