games/factorio-docker-bplein
1
0
Fork 0
mirror of https://github.com/bplein/factorio-docker.git synced 2025-01-26 03:52:15 +02:00
Code Issues Releases Activity
factorio-docker-bplein/0.16/Dockerfile

40 lines
1.2 KiB
Docker
Raw Normal View History

alpine 3.7
2018-01-09 14:59:21 -08:00
FROM frolvlad/alpine-glibc:alpine-3.7
added 0.16
2017-12-13 08:50:16 -08:00
MAINTAINER https://github.com/dtandersen/docker_factorio_server
run as factorio user
2017-12-13 18:33:51 +00:00
ARG USER=factorio
ARG GROUP=factorio
ARG PUID=845
ARG PGID=845
added 0.16
2017-12-13 08:50:16 -08:00
ENV PORT=34197 \
RCON_PORT=27015 \
update to 0.16.22
2018-02-02 09:08:50 +00:00
VERSION=0.16.22 \
SHA1=d6b6492bfc88052636ffdb51ac7aaa5f412d9b33
added 0.16
2017-12-13 08:50:16 -08:00
Fix volume permissions for docker-compose When using named containers in docker compose, it creates them with root and the factorio docker container fails to start because it doesn't have write permissions. Reproduce by using the following docker-compose file: version: '3.2' services: server: image: dtandersen/factorio:0.16.7 volumes: - logs:/var/log - data:/factorio ports: - "34197:34197/udp" - "27015:27015/tcp" volumes: logs: data: With this proposed change, the /factorio folder is created *before* it is made a volume. This causes docker to correctly preserve the permissions, the docker-compose file above works now. This is related to https://github.com/dtandersen/docker_factorio_server/issues/91 and maybe also makes https://github.com/dtandersen/docker_factorio_server/pull/99 obsolete.
2017-12-28 12:37:23 +00:00
RUN mkdir -p /opt /factorio && \
0.16.1
2017-12-13 21:17:41 +00:00
apk add --update --no-cache pwgen && \
added 0.16
2017-12-13 08:50:16 -08:00
apk add --update --no-cache --virtual .build-deps curl && \
curl -sSL https://www.factorio.com/get-download/$VERSION/headless/linux64 \
-o /tmp/factorio_headless_x64_$VERSION.tar.xz && \
echo "$SHA1 /tmp/factorio_headless_x64_$VERSION.tar.xz" | sha1sum -c && \
tar xf /tmp/factorio_headless_x64_$VERSION.tar.xz --directory /opt && \
don't need to make all of /opt/factorio writeable
2017-12-14 15:16:25 +00:00
chmod ugo=rwx /opt/factorio && \
added 0.16
2017-12-13 08:50:16 -08:00
rm /tmp/factorio_headless_x64_$VERSION.tar.xz && \
ln -s /factorio/saves /opt/factorio/saves && \
ln -s /factorio/mods /opt/factorio/mods && \
apk del .build-deps && \
run as factorio user
2017-12-13 18:33:51 +00:00
addgroup -g $PGID -S $GROUP && \
adduser -u $PUID -G $USER -s /bin/sh -SDH $GROUP && \
chown -R $USER:$GROUP /opt/factorio /factorio
added 0.16
2017-12-13 08:50:16 -08:00
Fix volume permissions for docker-compose When using named containers in docker compose, it creates them with root and the factorio docker container fails to start because it doesn't have write permissions. Reproduce by using the following docker-compose file: version: '3.2' services: server: image: dtandersen/factorio:0.16.7 volumes: - logs:/var/log - data:/factorio ports: - "34197:34197/udp" - "27015:27015/tcp" volumes: logs: data: With this proposed change, the /factorio folder is created *before* it is made a volume. This causes docker to correctly preserve the permissions, the docker-compose file above works now. This is related to https://github.com/dtandersen/docker_factorio_server/issues/91 and maybe also makes https://github.com/dtandersen/docker_factorio_server/pull/99 obsolete.
2017-12-28 12:37:23 +00:00
VOLUME /factorio
added 0.16
2017-12-13 08:50:16 -08:00
EXPOSE $PORT/udp $RCON_PORT/tcp
COPY ./docker-entrypoint.sh /
0.16.1
2017-12-13 21:17:41 +00:00
USER $USER
run as factorio user
2017-12-13 18:33:51 +00:00
ENTRYPOINT ["/docker-entrypoint.sh"]
Reference in New Issue Copy Permalink