binhex / arch-base

Docker build script for Arch Linux base

Application

Arch Linux

Description

Arch Linux is an independently developed, i686/x86-64 general purpose GNU/Linux distribution versatile enough to suit any role. Development focuses on simplicity, minimalism, and code elegance.

Build notes

Arch Linux base image built from "scratch". This image is set to a snapshot by using the archive.archlinux.org website for package updates, this is required to reduce image size by preventing rolling updates to packages.

Notes

This image includes dumb-init (https://github.com/Yelp/dumb-init) to ensure a clean shutdown and to correctly reap processes, Supervisor (http://supervisord.org/) is also installed to help monitor and run child processes.

If you appreciate my work, then please consider buying me a beer :D

Documentation | Support Forum

arch-base's Issues

Vulnerable xz Package in current Pacman Mirror List

A know backdoor was put into xz on versions of 5.6.0 and 5.6.1. I think I tracked it back to the right repo as the mirror list is pulling latest. The same site bytemark.co.uk has the updated version of 03-29-2024 at the time of opening this issue which should include 5.6.1-2. All versions of the image during the range of 02-24-2024 and 03-28-2024 are affected.

I confirmed from downstream privoxy-vpn that pacman -Q --info xz returns 5.6.1-1.

While right now archlinux isn't noted as impacted due to ssh implementation but ArchLinux is recommending updating immediately.

CVE-2024-3094 :
NIST
Red Hat

Sources:
ArchLinux
Upstream Report

Be able to choose which user radarr will run to

I'm trying to use this docker with plexdrive on my host, and because radarr runs inside the docker as the nobody user I can't have it interacting with my host folder unless it's also owned by nobody which is undesirable for me.

What would be the best way to achieve changing the user inside this docker image?

Would be cool if this could be just a flag you can set, and to be clear I tried using

-e UMASK=000 \
    -e PUID=1001 \
    -e PGID=1002 \

Which is my "automation" user in my host but in radarr I can't add my /mnt/unionfs/Movies to it because it's not writable by the user nobody.

I tried forking your docker and just editing this one, but it seems that it pulls from other dockers so I can't be sure of what all you did assuming a nobody user.

Thanks!

Filesystem corruption

I am using your docker image binhex/arch-rtorrentvpn and noticed after I pulled latest that it did not start. When looking into the logs I noticed that tmux failed to start with this error message no suitable socket path when I tried to ls /tmp I got a permission denied error. Turns out that something is wrong with the metadata in the filesystem.

Traced the error back to this image. Below is the same error I have in the arch-rtorrentvpn container. Reverted back to version binhex/arch-rtorrentvpn:rtorrent-ps-1.1.r54.ga787dd9-1-35 and that one works and the filesystem works as expected as well.

[root@e32c0123f2b0 /]# ls -la 
ls: cannot access '.': Operation not permitted
ls: cannot access 'etc': Operation not permitted
ls: cannot access '..': Operation not permitted
ls: cannot access 'proc': Operation not permitted
ls: cannot access 'sys': Operation not permitted
ls: cannot access 'dev': Operation not permitted
ls: cannot access '.dockerenv': Operation not permitted
ls: cannot access 'pkglist.x86_64.txt': Operation not permitted
ls: cannot access 'run': Operation not permitted
ls: cannot access 'opt': Operation not permitted
ls: cannot access 'sbin': Operation not permitted
ls: cannot access 'bin': Operation not permitted
ls: cannot access 'tmp': Operation not permitted
ls: cannot access 'home': Operation not permitted
ls: cannot access 'version': Operation not permitted
ls: cannot access 'mnt': Operation not permitted
ls: cannot access 'lib64': Operation not permitted
ls: cannot access 'var': Operation not permitted
ls: cannot access '.gnupg': Operation not permitted
ls: cannot access 'usr': Operation not permitted
ls: cannot access 'root': Operation not permitted
ls: cannot access 'boot': Operation not permitted
ls: cannot access 'srv': Operation not permitted
ls: cannot access 'lib': Operation not permitted
total 0
d????????? ? ? ? ?            ? .
d????????? ? ? ? ?            ? ..
l????????? ? ? ? ?            ? bin
d????????? ? ? ? ?            ? boot
d????????? ? ? ? ?            ? dev
-????????? ? ? ? ?            ? .dockerenv
d????????? ? ? ? ?            ? etc
d????????? ? ? ? ?            ? .gnupg
d????????? ? ? ? ?            ? home
l????????? ? ? ? ?            ? lib
l????????? ? ? ? ?            ? lib64
d????????? ? ? ? ?            ? mnt
d????????? ? ? ? ?            ? opt
-????????? ? ? ? ?            ? pkglist.x86_64.txt
d????????? ? ? ? ?            ? proc
d????????? ? ? ? ?            ? root
d????????? ? ? ? ?            ? run
l????????? ? ? ? ?            ? sbin
d????????? ? ? ? ?            ? srv
d????????? ? ? ? ?            ? sys
d????????? ? ? ? ?            ? tmp
d????????? ? ? ? ?            ? usr
d????????? ? ? ? ?            ? var
-????????? ? ? ? ?            ? version
[root@e32c0123f2b0 /]# 

getting supervisord to work correctly

Hello binhex,

I could use a bit of assistance. I am using this base repo to create an arch container for stuff.

Here is my Dockerfile:

FROM binhex/arch-base:2017102500
MAINTAINER binhex

ADD build/*.conf /etc/supervisor/conf.d/
ADD build/*.sh /arch/build/
ADD run/*.sh /arch/run/

RUN chmod +x /arch/build/*.sh /arch/run/*.sh && /bin/bash /arch/build/install.sh

VOLUME /config

EXPOSE 3000
EXPOSE 80

CMD ["/bin/bash", "/root/init.sh"]

My install:

#!/bin/bash

# exit script if return code != 0
set -e

# download build scripts from github
curl --connect-timeout 5 --max-time 600 --retry 5 --retry-delay 0 --retry-max-time 60 -o /tmp/scripts-master.zip -L https://github.com/binhex/scripts/archive/master.zip

# unzip build scripts
unzip /tmp/scripts-master.zip -d /tmp

# move shell scripts to /root
mv /tmp/scripts-master/shell/arch/docker/*.sh /root/

pacman_packages="git mongodb nodejs"

pacman -S --needed $pacman_packages --noconfirm

# cleanup
yes | pacman -Scc
rm -rf /usr/share/locale/*
rm -rf /usr/share/man/*
rm -rf /usr/share/gtk-doc/*
rm -rf /tmp/*

My supervisor conf:

[program:start-script]
autostart = true
autorestart = false
startsecs = 0
user = root
command = /arch/run/init.sh
stdout_logfile = /arch/log/init.out.log
stderr_logfile = /arch/log/init.err.log
umask = 000

[program:mongod]
autostart = true
autorestart = false
startsecs = 0
user = root
command = mongod
stdout_logfile = /arch/log/mongod.out.log
stderr_logfile = /arch/log/mongod.err.log
umask = 000

I can see supervisor starting correctly, and I can see the output loading my conf file:

Created by...
___.   .__       .__
\_ |__ |__| ____ |  |__   ____ ___  ___
 | __ \|  |/    \|  |  \_/ __ \\  \/  /
 | \_\ \  |   |  \   Y  \  ___/ >    <
 |___  /__|___|  /___|  /\___  >__/\_ \
     \/        \/     \/     \/      \/
   https://hub.docker.com/u/binhex/

2017-12-23 22:48:07.233409 [info] System information Linux de58e6619c7f 4.4.15+ #15217 SMP PREEMPT Wed Dec 20 18:19:46 CST 2017 x86_64 GNU/Linux
2017-12-23 22:48:07.394645 [warn] PUID not defined (via -e PUID), defaulting to '99'
2017-12-23 22:48:07.630342 [warn] PGID not defined (via -e PGID), defaulting to '100'
2017-12-23 22:48:08.496001 [warn] UMASK not defined (via -e UMASK), defaulting to '000'
2017-12-23 22:48:08.565417 [info] Permissions already set for volume mappings
2017-12-23 22:48:08.648115 [info] Starting Supervisor...
2017-12-23 22:48:11,170 CRIT Set uid to user 0
2017-12-23 22:48:11,170 INFO Included extra file "/etc/supervisor/conf.d/archlinux.conf" during parsing
2017-12-23 22:48:11,171 INFO supervisord started with pid 7
2017-12-23 22:48:12,172 INFO reaped unknown pid 8

All my services start correctly, but I cannot correctly stop/start services with supervisorctl.

When attempting to launch supervisorctl or when running supervisorctl restart, I see the following:

unix:///run/supervisor.sock no such file

I tried manually creating an empty file in that location and adding elevated permissions, but I just get the following:

unix:///run/supervisor.sock refused connection

I figured there was a trick you know that could help me get it going. Otherwise, everything is working perfectly.

Any help would be greatly appreciated.