Use debian:testing as base Docker build image instead of debian:sid one. This should resolve the problem which prevents the previous version (0.1.14-beta-release) from been built.
This commit is contained in:
@@ -1,5 +1,5 @@
|
|||||||
# Build the build base environment
|
# Build the build base environment
|
||||||
FROM debian:sid AS base
|
FROM debian:testing AS base
|
||||||
RUN set -ex && \
|
RUN set -ex && \
|
||||||
cd / && \
|
cd / && \
|
||||||
echo 'res=0; for i in $(seq 0 36); do $@; res=$?; [ $res -eq 0 ] && exit $res || sleep 10; done; exit $res' > /try.sh && chmod +x /try.sh && \
|
echo 'res=0; for i in $(seq 0 36); do $@; res=$?; [ $res -eq 0 ] && exit $res || sleep 10; done; exit $res' > /try.sh && chmod +x /try.sh && \
|
||||||
@@ -56,6 +56,7 @@ ENV SSHWIFTY_HOSTNAME= \
|
|||||||
SSHWIFTY_DOCKER_TLSCERT= \
|
SSHWIFTY_DOCKER_TLSCERT= \
|
||||||
SSHWIFTY_DOCKER_TLSCERTKEY=
|
SSHWIFTY_DOCKER_TLSCERTKEY=
|
||||||
COPY --from=builder /sshwifty /
|
COPY --from=builder /sshwifty /
|
||||||
|
COPY . /sshwifty-src
|
||||||
RUN set -ex && \
|
RUN set -ex && \
|
||||||
adduser -D sshwifty && \
|
adduser -D sshwifty && \
|
||||||
chmod +x /sshwifty && \
|
chmod +x /sshwifty && \
|
||||||
|
|||||||
Reference in New Issue
Block a user