build: add docker / container ignore files
What the developer wrote
Authored by Sjors Provoost
build: add docker / container ignore files
What changed, and why it matters
This commit adds two ignore files used when building Docker or container images. They simply tell the build tool which local files (like build leftovers, Python cache files, and documentation) should not be copied into the container image. There is no code change, no bug fix, and no apparent security issue.
No action required; this is a benign build configuration change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit introduces .dockerignore and .containerignore with identical content, excluding build artifacts, markdown files, Python bytecode/cache directories, virtualenvs, and dist directories from the container build context. This is a routine build-hygiene change.
Changed components
Docker/container build contextInspect captured patch +22 / −0
diff --git a/.containerignore b/.containerignore
new file mode 100644
index 0000000..895b580
--- /dev/null
+++ b/.containerignore
@@ -0,0 +1,11 @@
+# Exclude local build artifacts and any symlinks outside the context
+build*
+
+# Local documentation files (can be symlinks outside the context)
+*.md
+
+# Common Python / tooling artifacts
+__pycache__/
+*.pyc
+.venv/
+dist/
diff --git a/.dockerignore b/.dockerignore
new file mode 100644
index 0000000..895b580
--- /dev/null
+++ b/.dockerignore
@@ -0,0 +1,11 @@
+# Exclude local build artifacts and any symlinks outside the context
+build*
+
+# Local documentation files (can be symlinks outside the context)
+*.md
+
+# Common Python / tooling artifacts
+__pycache__/
+*.pyc
+.venv/
+dist/
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.