wetty/Dockerfile

FROM node:8-alpine as builder
WORKDIR /usr/src/app
RUN apk add --update build-base python
COPY . /usr/src/app
RUN yarn

FROM node:8-alpine
MAINTAINER butlerx@notthe.cloud
WORKDIR /app
RUN adduser -D -h /home/term -s /bin/sh term && \
    ( echo "term:term" | chpasswd ) && \
	apk add openssh-client
EXPOSE 3000
COPY --from=builder /usr/src/app /app
CMD node bin
Use multistage Dockerfile to cut down image size (#140) 6 years ago			`FROM node:8-alpine as builder`
			`WORKDIR /usr/src/app`
			`RUN apk add --update build-base python`
			`COPY . /usr/src/app`
			`RUN yarn`

use /usr/bin/env 8 years ago			`FROM node:8-alpine`
write ssh wrapper in shell 8 years ago			`MAINTAINER butlerx@notthe.cloud`
Create Dockerfile for wetty 11 years ago			`WORKDIR /app`
write ssh wrapper in shell 8 years ago			`RUN adduser -D -h /home/term -s /bin/sh term && \`
Provide SSH key option to specify client private key This is to make it possible for admins to enable password-less auth at the expense of security. In that situation: Server <=> Wetty <=> Client - Link between Wetty and the SSH Server is secured by SSH. - Wetty knows a private key to connect to the SSH Server, using an SSH User. - Client only needs to know how to access Wetty to run commands on the SSH Host. - Client would not be able to retrieve the private key from Wetty to login directly to the SSH Server. This basically means that anything that reaches Wetty needs to be trusted as it would be able to execute commands on the remote SSH server, so admins should be really careful when using that feature. 6 years ago			`( echo "term:term" \| chpasswd ) && \`
Use multistage Dockerfile to cut down image size (#140) 6 years ago			`apk add openssh-client`
Create Dockerfile for wetty 11 years ago			`EXPOSE 3000`
Use multistage Dockerfile to cut down image size (#140) 6 years ago			`COPY --from=builder /usr/src/app /app`
Dockerfile slimming (#139) * Use node instead of yarn in Dockerfile. Closes #134 * Don't install SSHD in container 6 years ago			`CMD node bin`