zeek/docker
Christian Kreibich 1dd6c1d716 Clean up fully after successful Docker btests
If we leave files sitting around, we trigger a Docker image double-build in CI,
because the build runs once, gets tested, and then gets run again when we push
the Docker image: the additional btest files cause Docker to detect a different
source tree, causing an image layer violation.

Also rename "cleanup" target to "clean", to align with rest of our tree.
2021-11-16 15:13:10 -08:00
..
btest Clean up fully after successful Docker btests 2021-11-16 15:13:10 -08:00
Dockerfile Enable customization of the Docker image's configure invocation 2021-09-30 08:41:21 -07:00
Makefile Test container with BTest instead of container-structure-tests 2021-09-24 11:48:49 +02:00
README Add a minimal containerized environment 2021-09-24 11:48:19 +02:00

Container image for Zeek
========================

This directory contains a minimal container image for Zeek. This image is
published automatically to [DockerHub](https://hub.docker.com/u/zeekurity) for
releases and for commits on the `master` branch.

- Images for release are published as
  [`zeekurity/zeek`](https://hub.docker.com/r/zeekurity/zeek) with the `latest`
  tag pointing to the latest release.
- Development images for the `master` branch are published as
  [`zeekurity/zeek-dev`](https://hub.docker.com/r/zeekurity/zeek-dev).


To run the image execute e.g.,:

    docker run -it zeekurity/zeek

To build the image execute `make` from this directory.