ff50274ff3
* Dockerfile: Support socat use cases In some contexts it is necessary to provide access to Gitea via TCP ports and unix sockets. Gitea (`gitea web`) can be configured to listen for connections via unix-socket or TCP port, but not both. When Gitea is installed to the host this limitation can be worked around by installing socat on the host. When running Gitea from a container this limitation cannot be workaround. Add socat to Gitea container. * Removed version Co-authored-by: techknowlogick <techknowlogick@gitea.io>
66 lines
1.3 KiB
Docker
66 lines
1.3 KiB
Docker
|
|
###################################
|
|
#Build stage
|
|
FROM golang:1.15-alpine3.12 AS build-env
|
|
|
|
ARG GOPROXY
|
|
ENV GOPROXY ${GOPROXY:-direct}
|
|
|
|
ARG GITEA_VERSION
|
|
ARG TAGS="sqlite sqlite_unlock_notify"
|
|
ENV TAGS "bindata timetzdata $TAGS"
|
|
ARG CGO_EXTRA_CFLAGS
|
|
|
|
#Build deps
|
|
RUN apk --no-cache add build-base git nodejs npm
|
|
|
|
#Setup repo
|
|
COPY . ${GOPATH}/src/code.gitea.io/gitea
|
|
WORKDIR ${GOPATH}/src/code.gitea.io/gitea
|
|
|
|
#Checkout version if set
|
|
RUN if [ -n "${GITEA_VERSION}" ]; then git checkout "${GITEA_VERSION}"; fi \
|
|
&& make clean-all build
|
|
|
|
FROM alpine:3.12
|
|
LABEL maintainer="maintainers@gitea.io"
|
|
|
|
EXPOSE 22 3000
|
|
|
|
RUN apk --no-cache add \
|
|
bash \
|
|
ca-certificates \
|
|
curl \
|
|
gettext \
|
|
git \
|
|
linux-pam \
|
|
openssh \
|
|
s6 \
|
|
sqlite \
|
|
socat \
|
|
su-exec \
|
|
gnupg
|
|
|
|
RUN addgroup \
|
|
-S -g 1000 \
|
|
git && \
|
|
adduser \
|
|
-S -H -D \
|
|
-h /data/git \
|
|
-s /bin/bash \
|
|
-u 1000 \
|
|
-G git \
|
|
git && \
|
|
echo "git:$(dd if=/dev/urandom bs=24 count=1 status=none | base64)" | chpasswd
|
|
|
|
ENV USER git
|
|
ENV GITEA_CUSTOM /data/gitea
|
|
|
|
VOLUME ["/data"]
|
|
|
|
ENTRYPOINT ["/usr/bin/entrypoint"]
|
|
CMD ["/bin/s6-svscan", "/etc/s6"]
|
|
|
|
COPY docker/root /
|
|
COPY --from=build-env /go/src/code.gitea.io/gitea/gitea /app/gitea/gitea
|
|
RUN ln -s /app/gitea/gitea /usr/local/bin/gitea
|