docker/start.sh

#!/bin/sh

# Bind linked docker container to localhost socket using socat
env | sed -En 's|(.*)_PORT_([0-9]*)_TCP=tcp://(.*):(.*)|\1_\2 socat -ls TCP4-LISTEN:\2,fork,reuseaddr TCP4:\3:\4|p' | \
while read NAME CMD; do
    mkdir -p /app/gogs/docker/s6/$NAME
    echo -e "#!/bin/sh\nexec $CMD" > /app/gogs/docker/s6/$NAME/run
    chmod +x /app/gogs/docker/s6/$NAME/run
done

# Exec S6 as process manager for gogs and dropbear ssh
exec /usr/bin/s6-svscan /app/gogs/docker/s6/
New approach to Gogs Docker Container - VOLUME for ‘/data’ - Usage of S6 as PID 1 Process - Usage of ‘socat’ so linked container (like databases) are binded to localhost - OpenSSH, Socat Link and Gogs are supervised using S6 - Size of container reduced to ~75Mo 2015-10-02 10:56:36 +01:00			`#!/bin/sh`

			`# Bind linked docker container to localhost socket using socat`
			`env \| sed -En 's\|(.)_PORT_([0-9])_TCP=tcp://(.):(.)\|\1_\2 socat -ls TCP4-LISTEN:\2,fork,reuseaddr TCP4:\3:\4\|p' \| \`
			`while read NAME CMD; do`
			`mkdir -p /app/gogs/docker/s6/$NAME`
			`echo -e "#!/bin/sh\nexec $CMD" > /app/gogs/docker/s6/$NAME/run`
			`chmod +x /app/gogs/docker/s6/$NAME/run`
			`done`

			`# Exec S6 as process manager for gogs and dropbear ssh`
			`exec /usr/bin/s6-svscan /app/gogs/docker/s6/`