move Dockerfile to the right folder

Author: Jiloc

Dockerfile

@@ -1,25 +1,16 @@
-# Use a specific nightly toolchain for reproducible builds
-FROM rustlang/rust@sha256:04690ffa09cddd358b349272173155319f384e57816614eea0840ec7f9422862
+FROM rust:bookworm AS build
 
-# Set the working directory for building
-WORKDIR /build
+ARG STACKS_NODE_VERSION="No Version Info"
+ARG GIT_BRANCH='No Branch Info'
+ARG GIT_COMMIT='No Commit Info'
 
-# Copy the entire project to build the binaries
+WORKDIR /src
 COPY . .
+RUN mkdir /out
+RUN rustup toolchain install stable
+RUN cargo build --features monitoring_prom,slog_json --release
+RUN cp -R target/release/. /out
 
-# Pre-build the config-docs-generator binaries during image build
-RUN cargo build --package config-docs-generator --release
-
-# Set the working directory where the project will be mounted at runtime
-WORKDIR /project_root
-
-# Set environment variables for generate-config-docs.sh
-ENV PROJECT_ROOT=/project_root
-ENV BUILD_ROOT=/build
-ENV CARGO_HOME=/project_root/.cargo
-ENV EXTRACT_DOCS_BIN=/build/target/release/extract-docs
-ENV GENERATE_MARKDOWN_BIN=/build/target/release/generate-markdown
-ENV SKIP_BUILD=true
-
-# Set the entrypoint to run the config docs generation script
-ENTRYPOINT ["/build/contrib/tools/config-docs-generator/generate-config-docs.sh"]
+FROM debian:bookworm-slim
+COPY --from=build /out/stacks-node /out/stacks-signer /out/stacks-inspect /bin/
+CMD ["stacks-node", "mainnet"]

contrib/tools/config-docs-generator/Dockerfile

@@ -0,0 +1,27 @@
+# Use a specific nightly toolchain for reproducible builds
+FROM rustlang/rust@sha256:04690ffa09cddd358b349272173155319f384e57816614eea0840ec7f9422862
+
+# Set the working directory for building
+WORKDIR /build
+
+# Copy the entire project root to preserve structure
+# Copy from three levels up (project root) to maintain the directory structure
+COPY ../../../ /build
+
+# Pre-build the config-docs-generator binaries during image build
+RUN cargo build --package config-docs-generator --release
+
+# Set the working directory where the project will be mounted at runtime
+WORKDIR /project_root
+
+# Set environment variables for generate-config-docs.sh
+ENV PROJECT_ROOT=/project_root
+ENV BUILD_ROOT=/build
+ENV CARGO_HOME=/project_root/.cargo
+ENV EXTRACT_DOCS_BIN=/build/target/release/extract-docs
+ENV GENERATE_MARKDOWN_BIN=/build/target/release/generate-markdown
+ENV SKIP_BUILD=true
+
+# Set the entrypoint to run the config docs generation script
+# The script ends up at /build/generate-config-docs.sh due to the copy operation
+ENTRYPOINT ["/build/generate-config-docs.sh"]

contrib/tools/config-docs-generator/README.md

@@ -13,7 +13,7 @@ The easiest way to generate configuration documentation:
 docker build -t config-docs-generator .
 
 # Generate documentation
-docker run --rm -v "$(pwd):/project_root" --user "$(id -u):$(id -g)" config-docs-generator
+docker run --rm -v "$(pwd)/../../../:/project_root" config-docs-generator
 ```
 
 This approach:
@@ -117,7 +117,7 @@ fn struct_to_section_name(struct_name: &str) -> String {
 
 ```bash
 # Using Docker (recommended)
-docker run --rm -v "$(pwd):/project_root" --user "$(id -u):$(id -g)" config-docs-generator
+docker run --rm -v "$(pwd)/../../../:/project_root" config-docs-generator
 
 # OR using local setup
 ./contrib/tools/config-docs-generator/generate-config-docs.sh