Rename busybox_HTTPD to busybox-httpd and clarify new CMD call

lipanski · May 7, 2024 · 295afd8 · 295afd8
1 parent d1d7862
commit 295afd8
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/Dockerfile b/Dockerfile
@@ -32,7 +32,7 @@ EXPOSE 3000
 COPY --from=builder /etc/passwd /etc/passwd
 
 # Copy the static binary
-COPY --from=builder /busybox/busybox_HTTPD /busybox_HTTPD
+COPY --from=builder /busybox/busybox_HTTPD /busybox-httpd
 
 # Use our non-root user
 USER static
@@ -50,4 +50,4 @@ COPY httpd.conf .
 # COPY . .
 
 # Run busybox httpd
-CMD ["/busybox_HTTPD", "-f", "-v", "-p", "3000", "-c", "httpd.conf"]
+CMD ["/busybox-httpd", "-f", "-v", "-p", "3000", "-c", "httpd.conf"]
diff --git a/README.md b/README.md
@@ -39,7 +39,7 @@ FROM lipanski/docker-static-website:latest
 # Copy your static files
 COPY . .
 
-CMD ["/busybox", "httpd", "-f", "-v", "-p", "3000", "-c", "httpd.conf"]
+CMD ["/busybox-httpd", "-f", "-v", "-p", "3000", "-c", "httpd.conf"]
 ```
 
 **NOTE:** Sending a `TERM` signal to your TTY running the container won't get propagated due to how busybox is built. Instead you can call `docker stop` (or `docker kill` if can't wait 15 seconds). Alternatively you can run the container with `docker run -it --rm --init` which will propagate signals to the process correctly.