Build images

Makefile

@@ -1,4 +1,14 @@
 .PHONY: build
 
 build:
-	cargo build --release
+	cargo build --release
+
+image-amd64:
+	docker build -f image/Dockerfile --platform amd64 -t wasm-workers-server:latest-amd64 .
+
+image-arm64:
+	docker build -f image/Dockerfile --platform arm64 -t wasm-workers-server:latest-arm64 .
+
+push-image-multiarch:
+	docker buildx build -f image/Dockerfile --platform linux/arm64/v8,linux/amd64 --push -t projects.registry.vmware.com/wasmlabs/containers/wasm-workers-server:latest .
+

README.md

@@ -73,6 +73,20 @@ curl https://raw.githubusercontent.com/vmware-labs/wasm-workers-server/main/inst
   ./wws --help
 ```
 
+### Running in a container
+
+If you don't want to install anything locally you can just run `wws` from the `projects.registry.vmware.com/wasmlabs/containers/wasm-workers-server:latest` container image. All you need to do is:
+
+ - map a local folder with handlers to `/app` within the container
+ - expose port `8080` from the container
+
+Here is how to quickly run a container with an ad-hoc handler from the /tmp/wws-app folder:
+
+```bash
+mkdir /tmp/wws-app 2>/dev/null;
+echo 'addEventListener("fetch", (e) => { return e.respondWith(new Response("Hello from WWS\n"));});' > /tmp/wws-app/index.js;
+docker run --rm -v /tmp/wws-app:/app -p 8080:8080 projects.registry.vmware.com/wasmlabs/containers/wasm-workers-server:latest
+```
 ## Language Support
 
 Wasm Workers Server focuses on simplicity. We want you to run handlers (written in different languages) safely in WebAssembly. For interpreted languages, we add different interpreters:

docs/docs/containers.md

@@ -0,0 +1,26 @@
+---
+sidebar_position: 3
+---
+
+# Running in a container
+
+For convenience we have published a container image that contains Wasm Workers Server. It is available at `projects.registry.vmware.com/wasmlabs/containers/wasm-workers-server:latest`. Any container that runs it will get the `wws` binary, running and:
+
+ - looking for worker handlers in the `/app` folder
+ - listening on `0.0.0.0:8080` inside the container
+
+The image is based on `debian:bullseye-slim` + the `wws` binary. It includes support for the `linux/amd64` and `linux/arm64/v8` platforms. The image size should be around `~100MiB`
+
+## Running a local container
+
+A typical one-liner to run a local container for development purposes would look like:
+
+```bash
+docker run -v /path/to/handlers/on/host:/app -p 8080:8080 \
+ projects.registry.vmware.com/wasmlabs/containers/wasm-workers-server:latest
+```
+
+## Other usages
+
+Wasm Workers Server is stateless as far as the loaded handers are stateless (i.e. when they don't use the [Key / Value store](../features/key-value.md)). This makes the image very useful if you want to setup your own auto-scaling deployment.
+

docs/docs/how-it-works.md

@@ -1,5 +1,5 @@
 ---
-sidebar_position: 3
+sidebar_position: 4
 ---
 
 # How it works?

image/Dockerfile

@@ -0,0 +1,31 @@
+# Build wasm_runtime in release mode
+
+
+FROM --platform=$TARGETPLATFORM rust:1.64.0-slim as build-wws
+ARG WWS_BUILD_DIR=/usr/src/wws
+ARG TARGETPLATFORM
+ARG BUILDPLATFORM
+WORKDIR $WWS_BUILD_DIR
+COPY ./ $WWS_BUILD_DIR/
+RUN echo "Running on ${BUILDPLATFORM}, building for ${TARGETPLATFORM}"
+RUN set -eux; \
+    ls -l .; \
+    case "${TARGETPLATFORM}" in \
+        linux/amd64) bldArch='x86_64-unknown-linux-gnu' ;; \
+        linux/arm64) bldArch='aarch64-unknown-linux-gnu' ;; \
+        *) echo >&2 "unsupported architecture: $BUILDPLATFORM"; exit 1 ;; \
+    esac; \
+    rustup target add $bldArch; \
+    cargo build --release --target=$bldArch; \
+    mkdir ./build; \
+    cp ./target/$bldArch/release/wws ./build/wws
+
+
+FROM --platform=$TARGETPLATFORM debian:bullseye-slim
+ARG WWS_BUILD_DIR=/usr/src/wws
+RUN mkdir -p /app
+RUN mkdir -p /opt
+COPY --from=build-wws ${WWS_BUILD_DIR}/build/wws /opt
+
+CMD ["/opt/wws", "/app/", "--host", "0.0.0.0"]
+