fleet/Dockerfile

FROM alpine
MAINTAINER Fleet Developers <hello@fleetdm.com>

RUN apk --update add ca-certificates

# Create FleetDM group and user
RUN addgroup -S fleet && adduser -S fleet -G fleet

COPY ./build/binary-bundle/linux/fleet ./build/binary-bundle/linux/fleetctl /usr/bin/

USER fleet
CMD ["fleet", "serve"]
Make it harder to accidentally release macOS binaries (#1566) 2017-10-16 23:35:14 +00:00			`FROM alpine`
Remove @fleetdm.com emails from fleetdm/fleet repo (#882) - In tests and documentation, replace `@fleetdm.com` with `@example.com` - In documentation, replace `hello@fleetdm.com` with `fleetdm.com/contact` - In documentation, replace `security@fleetdm.com` with `fleetdm.com/contact` - In Dockerfiles, replace `engineering@fleetdm.com` with `hello@fleetdm.com`. These two files are the only remaining files with a `@fleetdm.com` email. 2021-05-27 21:19:14 +00:00			`MAINTAINER Fleet Developers <hello@fleetdm.com>`
add Dockerfile (#94) * add Dockerfile to build 2016-08-25 13:25:02 +00:00
Make it harder to accidentally release macOS binaries (#1566) 2017-10-16 23:35:14 +00:00			`RUN apk --update add ca-certificates`
add system roots to alpine container. (#890) Fixes #889 2017-01-11 06:39:14 +00:00
Updated .dockerignore and added non-root user to Dockerfile (#143) Running applications as root (default Docker user) is not a good security practice. The goal of this PR is to run the Fleet application as a non-root user. For development you can still access the container as root with the following command: `docker run -it --user=0 <fleetdm container ID> bash` 2020-12-22 16:23:17 +00:00			`# Create FleetDM group and user`
			`RUN addgroup -S fleet && adduser -S fleet -G fleet`

Add fleetctl to generated Docker images (#1896) 2018-08-08 23:21:49 +00:00			`COPY ./build/binary-bundle/linux/fleet ./build/binary-bundle/linux/fleetctl /usr/bin/`
add Dockerfile (#94) * add Dockerfile to build 2016-08-25 13:25:02 +00:00
Updated .dockerignore and added non-root user to Dockerfile (#143) Running applications as root (default Docker user) is not a good security practice. The goal of this PR is to run the Fleet application as a non-root user. For development you can still access the container as root with the following command: `docker run -it --user=0 <fleetdm container ID> bash` 2020-12-22 16:23:17 +00:00			`USER fleet`
Make it harder to accidentally release macOS binaries (#1566) 2017-10-16 23:35:14 +00:00			`CMD ["fleet", "serve"]`