{"slug":"dockerfile","title":"Dockerfile","extensions":["Dockerfile",".dockerfile"],"entry_languages":["Dockerfile"],"prompts":33,"repos":0,"sample":[],"tools":[],"headline":[],"raw_md":"https://awesomereviewers.com/raw/verify/dockerfile.md","raw_json":"https://awesomereviewers.com/raw/verify/dockerfile.json","url":"https://awesomereviewers.com/verify/dockerfile/","baseline":{"slug":"every-change","title":"Any change","topics":["Code Style","Naming Conventions"],"checks":[{"kind":"formatting","title":"Formatting","method":"formatting","method_slug":"formatting","catches":"Layout drift that buries the real change in the diff.","tool":null,"alternatives":[],"note":null},{"kind":"linting","title":"Linting","method":"static_analysis","method_slug":"static-analysis","catches":"Bug-prone patterns, unused code and conventions the formatter does not cover.","tool":null,"alternatives":[],"note":null},{"kind":"type-checking","title":"Type checking","method":"static_analysis","method_slug":"static-analysis","catches":"Wrong types, unhandled null or None, call signatures broken across modules.","tool":null,"alternatives":[],"note":null},{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},"changes":[{"slug":"security","title":"Authentication, input handling, secrets, permissions","topics":["Security"],"checks":[{"kind":"security-scanning","title":"Security scanning","method":"static_analysis","method_slug":"static-analysis","catches":"Injection, unsafe APIs and tainted data reaching a sink.","tool":null,"alternatives":[],"note":null},{"kind":"secret-scanning","title":"Secret scanning","method":"static_analysis","method_slug":"static-analysis","catches":"Credentials and tokens committed to the repository.","tool":null,"alternatives":[],"note":null},{"kind":"dependency-audit","title":"Dependency audit","method":"supply_chain","method_slug":"supply-chain","catches":"Known-vulnerable or disallowed dependencies and licenses.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"comfyui-container-security-best-practices","title":"Container security best practices","description":"Implement comprehensive security measures in containerized applications to prevent privilege escalation, injection attacks, and unauthorized access. This includes proper user configuration, variable quoting, and secure process handling.","repository":"comfyanonymous/ComfyUI","domain":"ml-systems","topic":"Security","language":"Dockerfile","updated":"2025-02-23","comments":2,"stars":83726,"raw":"https://awesomereviewers.com/raw/comfyui-container-security-best-practices.md"},{"slug":"agentcore-samples-ignore-secrets-in-images","title":"Ignore secrets in images","description":"When building container images, never copy the entire build context blindly. Add a `.dockerignore` (and/or use targeted `COPY` paths) to ensure sensitive files and local artifacts can’t be baked into the image—especially when using `COPY . .`.","repository":"awslabs/agentcore-samples","domain":"ai-agents","topic":"Security","language":"Dockerfile","updated":"2026-07-23","comments":1,"stars":3244,"raw":"https://awesomereviewers.com/raw/agentcore-samples-ignore-secrets-in-images.md"},{"slug":"bifrost-harden-build-time-paths","title":"Harden build-time paths","description":"When Dockerfile (or build scripts) use build-args/variables to choose target directories for `chown`/`chmod`, validate those paths at build time and fail if they target sensitive directories. This prevents overly-permissive ownership (e.g., group 0 write access) from becoming reachable via undocumented/override knobs.","repository":"maximhq/bifrost","domain":"llm-infra","topic":"Security","language":"Dockerfile","updated":"2026-07-04","comments":1,"stars":6862,"raw":"https://awesomereviewers.com/raw/bifrost-harden-build-time-paths.md"},{"slug":"omniroute-disable-install-scripts","title":"Disable install scripts","description":"In security-sensitive build environments (e.g., Docker/CI), prevent dependency install/postinstall hooks from executing arbitrary code. Use `npm ci` with `--ignore-scripts` to reduce supply-chain risk, but explicitly rebuild and validate any known native/runtime dependency that truly must compile/bind for the target platform.","repository":"diegosouzapw/OmniRoute","domain":"llm-infra","topic":"Security","language":"Dockerfile","updated":"2026-05-27","comments":1,"stars":33162,"raw":"https://awesomereviewers.com/raw/omniroute-disable-install-scripts.md"},{"slug":"n8n-avoid-hardcoded-credentials","title":"Avoid hardcoded credentials","description":"Never hardcode sensitive information such as passwords, API keys, or authentication tokens in source code, configuration files, or container definitions. These can be exposed through version control systems, shared repositories, or compromised container images.","repository":"n8n-io/n8n","domain":"ai-agents","topic":"Security","language":"Dockerfile","updated":"2025-07-17","comments":1,"stars":122978,"raw":"https://awesomereviewers.com/raw/n8n-avoid-hardcoded-credentials.md"},{"slug":"neon-prefer-opt-in-security","title":"Prefer opt-in security","description":"When implementing security features that modify data presentation or alter normal data access patterns (like anonymization, masking, or redaction), design them to be explicitly enabled by users rather than activated by default. Default-enabled data transformation creates security and usability concerns as users may not expect or desire their data to be...","repository":"neondatabase/neon","domain":"data-systems","topic":"Security","language":"Dockerfile","updated":"2025-04-28","comments":1,"stars":19015,"raw":"https://awesomereviewers.com/raw/neon-prefer-opt-in-security.md"},{"slug":"volcano-avoid-unnecessary-privilege-tools","title":"avoid unnecessary privilege tools","description":"Do not install privilege escalation tools like sudo, su, or doas in containers unless they are explicitly required for the application's functionality. Most containers run as root by default, making sudo redundant and potentially creating security vulnerabilities by expanding the attack surface.","repository":"volcano-sh/volcano","domain":"orchestration","topic":"Security","language":"Dockerfile","updated":"2025-03-03","comments":1,"stars":4899,"raw":"https://awesomereviewers.com/raw/volcano-avoid-unnecessary-privilege-tools.md"},{"slug":"kafka-secure-gpg-verification","title":"Secure GPG verification","description":"When downloading and verifying packages using GPG signatures, follow secure practices to ensure authenticity and prevent security vulnerabilities. Use hardcoded GPG keys rather than dynamic ones, employ reliable keyservers, set proper GNUPGHOME environment, and clean up GPG processes after verification.","repository":"apache/kafka","domain":"data-systems","topic":"Security","language":"Dockerfile","updated":"2024-08-13","comments":1,"stars":30575,"raw":"https://awesomereviewers.com/raw/kafka-secure-gpg-verification.md"},{"slug":"kubeflow-harden-container-security","title":"Harden container security","description":"When building container images, ensure they''re compatible with restricted Kubernetes security contexts. Use numeric UIDs instead of symbolic usernames, and test compatibility with the following security constraints:","repository":"kubeflow/kubeflow","domain":"ml-systems","topic":"Security","language":"Dockerfile","updated":"2024-06-30","comments":1,"stars":15064,"raw":"https://awesomereviewers.com/raw/kubeflow-harden-container-security.md"},{"slug":"frp-non-root-container-users","title":"Non-root container users","description":"Always run containers with a non-root user to reduce the security attack surface. Modern Docker allows non-root users to bind to privileged ports (80, 443), eliminating a common reason for using root. Create a dedicated user and group in your Dockerfile and ensure your application runs with that user's privileges.","repository":"fatedier/frp","domain":"cloud-infra","topic":"Security","language":"Dockerfile","updated":"2023-10-31","comments":1,"stars":95938,"raw":"https://awesomereviewers.com/raw/frp-non-root-container-users.md"}],"prompt_count":10},{"slug":"interfaces","title":"Public APIs, signatures, error paths, nullability","topics":["API","Error Handling","Null Handling"],"checks":[{"kind":"type-checking","title":"Type checking","method":"static_analysis","method_slug":"static-analysis","catches":"Wrong types, unhandled null or None, call signatures broken across modules.","tool":null,"alternatives":[],"note":null},{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"property-tests","title":"Property-based tests","method":"testing","method_slug":"testing","catches":"Edge-case inputs nobody wrote a test for; invariants over generated data.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"services","title":"Service and framework code","topics":["Fastify","NestJS","Spring","Axum","Celery","Temporal"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"algorithms","title":"Algorithms, parsers, data transforms","topics":["Algorithms"],"checks":[{"kind":"property-tests","title":"Property-based tests","method":"testing","method_slug":"testing","catches":"Edge-case inputs nobody wrote a test for; invariants over generated data.","tool":null,"alternatives":[],"note":null},{"kind":"fuzzing","title":"Fuzzing","method":"testing","method_slug":"testing","catches":"Crashes, panics and hangs on malformed input, especially in parsers and decoders.","tool":null,"alternatives":[],"note":null},{"kind":"mutation-testing","title":"Mutation testing","method":"testing","method_slug":"testing","catches":"Tests that keep passing whatever the code does.","tool":null,"alternatives":[],"note":null},{"kind":"proofs","title":"Proofs and specifications","method":"formal","method_slug":"formal","catches":"Design-level bugs in protocols and algorithms, checked against a specification.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"concurrency","title":"Threads, async code, locks, shared state","topics":["Concurrency"],"checks":[{"kind":"concurrency-model-checking","title":"Concurrency model checking","method":"formal","method_slug":"formal","catches":"Races and orderings that fail only under specific interleavings.","tool":null,"alternatives":[],"note":null},{"kind":"ub-detection","title":"Undefined-behaviour detection","method":"formal","method_slug":"formal","catches":"Memory-safety and aliasing violations in unsafe code.","tool":null,"alternatives":[],"note":null},{"kind":"property-tests","title":"Property-based tests","method":"testing","method_slug":"testing","catches":"Edge-case inputs nobody wrote a test for; invariants over generated data.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"networking","title":"Network calls, retries, timeouts, protocols","topics":["Networking","Axios"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"fuzzing","title":"Fuzzing","method":"testing","method_slug":"testing","catches":"Crashes, panics and hangs on malformed input, especially in parsers and decoders.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"kubeflow-standardize-network-tools","title":"Standardize network tools","description":"When performing network operations in build scripts or containers, prefer `curl` over `wget` for HTTP requests to standardize dependencies and improve portability. Use the specific flags `-fsSL` for silent operation with proper error handling, and explicitly specify output destinations.","repository":"kubeflow/kubeflow","domain":"ml-systems","topic":"Networking","language":"Dockerfile","updated":"2024-08-21","comments":4,"stars":15064,"raw":"https://awesomereviewers.com/raw/kubeflow-standardize-network-tools.md"}],"prompt_count":1},{"slug":"ui","title":"UI components and pages","topics":["React","Next","Next.js","Vue","Angular"],"checks":[{"kind":"browser-tests","title":"End-to-end browser tests","method":"testing","method_slug":"testing","catches":"User flows broken across components, routing and the network.","tool":null,"alternatives":[],"note":null},{"kind":"linting","title":"Linting","method":"static_analysis","method_slug":"static-analysis","catches":"Bug-prone patterns, unused code and conventions the formatter does not cover.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"data","title":"Databases, migrations, caching","topics":["Database","Migrations","Caching"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"uv-cache-sharing-strategy","title":"Cache sharing strategy","description":"When implementing caching in build systems, carefully configure cache sharing behavior based on your concurrency requirements. Improper sharing settings can lead to build failures when multiple processes attempt to access the same cache simultaneously.","repository":"astral-sh/uv","domain":"devtools","topic":"Caching","language":"Dockerfile","updated":"2025-04-29","comments":2,"stars":60322,"raw":"https://awesomereviewers.com/raw/uv-cache-sharing-strategy.md"}],"prompt_count":1},{"slug":"performance","title":"Hot paths and performance","topics":["Performance Optimization"],"checks":[],"prompts":[{"slug":"celery-split-dependency-installs","title":"Split Dependency Installs","description":"When building Docker images, optimize dependency installation for both caching and resource limits. Apply these rules: 1) **Maximize layer caching:** install Python requirements *before* copying your application source.","repository":"celery/celery","domain":"orchestration","topic":"Performance Optimization","language":"Dockerfile","updated":"2026-01-17","comments":3,"stars":28464,"raw":"https://awesomereviewers.com/raw/celery-split-dependency-installs.md"}],"prompt_count":1},{"slug":"ai","title":"Model, prompt and LLM code","topics":["AI","Pytorch"],"checks":[{"kind":"unit-tests","title":"Unit and integration tests","method":"testing","method_slug":"testing","catches":"Behaviour regressions on the paths the tests exercise.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"sglang-cuda-compatibility-verification","title":"CUDA compatibility verification","description":"When modifying CUDA versions or GPU architecture configurations in AI/ML projects, verify compatibility across three critical dimensions: CUDA version support, GPU architecture coverage, and dependent library requirements. Check official compatibility matrices, test with target hardware, and validate that AI libraries maintain their functionality.","repository":"sgl-project/sglang","domain":"llm-infra","topic":"AI","language":"Dockerfile","updated":"2025-07-18","comments":2,"stars":17245,"raw":"https://awesomereviewers.com/raw/sglang-cuda-compatibility-verification.md"}],"prompt_count":1},{"slug":"observability","title":"Logging, metrics, tracing","topics":["Logging","Observability"],"checks":[],"prompts":[],"prompt_count":0},{"slug":"ci-config","title":"CI workflows and configuration files","topics":["CI/CD","Configurations"],"checks":[{"kind":"workflow-linting","title":"CI workflow linting","method":"static_analysis","method_slug":"static-analysis","catches":"Broken GitHub Actions syntax, script injection, over-broad token permissions.","tool":null,"alternatives":[],"note":null},{"kind":"file-hygiene","title":"File hygiene","method":"formatting","method_slug":"formatting","catches":"Invalid JSON, YAML or TOML, merge markers, trailing whitespace, oversized files.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"kubeflow-environment-variable-management","title":"Environment variable management","description":"Manage environment variables in Docker configurations with appropriate scope, placement, and documentation: 1. **Set environment variables with appropriate scope**:","repository":"kubeflow/kubeflow","domain":"ml-systems","topic":"Configurations","language":"Dockerfile","updated":"2024-08-23","comments":5,"stars":15064,"raw":"https://awesomereviewers.com/raw/kubeflow-environment-variable-management.md"},{"slug":"celery-environment-consistent-builds","title":"Environment-consistent builds","description":"When building/installing Python dependencies in Docker/CI for multiple Python versions, keep the environment deterministic and aligned across interpreters: use the same dependency constraint/lock inputs everywhere and ensure the packaging toolchain is consistent per interpreter.","repository":"celery/celery","domain":"orchestration","topic":"Configurations","language":"Dockerfile","updated":"2026-02-10","comments":3,"stars":28464,"raw":"https://awesomereviewers.com/raw/celery-environment-consistent-builds.md"},{"slug":"browser-use-optimize-docker-layers","title":"optimize Docker layers","description":"Avoid unnecessary duplication and bloat in Docker layers by trusting base images to provide standard tools and using appropriate installation methods. Instead of upgrading pip when the base image already provides it, trust the image's version to prevent duplicate copies across layers. When installing application code, use editable installs to avoid creating...","repository":"browser-use/browser-use","domain":"ai-agents","topic":"Configurations","language":"Dockerfile","updated":"2025-05-10","comments":3,"stars":69139,"raw":"https://awesomereviewers.com/raw/browser-use-optimize-docker-layers.md"},{"slug":"poetry-pin-configuration-versions","title":"Pin configuration versions","description":"Always pin specific versions for base images, dependencies, and environment configurations to ensure reproducible builds and prevent unexpected failures from upstream changes.","repository":"python-poetry/poetry","domain":"devtools","topic":"Configurations","language":"Dockerfile","updated":"2025-03-10","comments":3,"stars":33496,"raw":"https://awesomereviewers.com/raw/poetry-pin-configuration-versions.md"},{"slug":"comfyui-environment-variable-consistency","title":"Environment variable consistency","description":"Ensure consistent formatting and proper usage of environment variables in Dockerfiles. Remove unnecessary quotes from ENV declarations and choose between ARG and ENV based on their intended scope - use ARG for build-time configuration that may change between builds, and ENV for runtime configuration that containers need during execution.","repository":"comfyanonymous/ComfyUI","domain":"ml-systems","topic":"Configurations","language":"Dockerfile","updated":"2025-01-11","comments":3,"stars":83726,"raw":"https://awesomereviewers.com/raw/comfyui-environment-variable-consistency.md"},{"slug":"compose-pin-build-dependency-versions","title":"Pin build dependency versions","description":"Always pin specific versions for build dependencies and tools to prevent unexpected build failures, even when the dependency won't be shipped in the final product. While rolling tags may be convenient, explicit version pinning provides build reproducibility and prevents surprises from automatic updates.","repository":"docker/compose","domain":"orchestration","topic":"Configurations","language":"Dockerfile","updated":"2023-08-10","comments":3,"stars":35858,"raw":"https://awesomereviewers.com/raw/compose-pin-build-dependency-versions.md"},{"slug":"kafka-centralize-configuration-values","title":"Centralize configuration values","description":"Avoid duplicating configuration values across multiple files by maintaining a single source of truth for environment variables, build arguments, version specifications, and other configuration parameters. When the same value appears in build scripts, Dockerfiles, documentation, or configuration files, consolidate it to one authoritative location and...","repository":"apache/kafka","domain":"data-systems","topic":"Configurations","language":"Dockerfile","updated":"2025-07-16","comments":2,"stars":30575,"raw":"https://awesomereviewers.com/raw/kafka-centralize-configuration-values.md"},{"slug":"prowler-parameterize-configuration-values","title":"Parameterize configuration values","description":"Always extract configuration values (like versions, paths, or other changeable settings) into parameters rather than hardcoding them directly in multiple places. This creates a single source of truth, simplifies updates, and makes your code more maintainable.","repository":"prowler-cloud/prowler","domain":"security","topic":"Configurations","language":"Dockerfile","updated":"2025-04-29","comments":2,"stars":11834,"raw":"https://awesomereviewers.com/raw/prowler-parameterize-configuration-values.md"},{"slug":"uv-optimize-docker-build-caching","title":"Optimize docker build caching","description":"Leverage Docker BuildKit's cache and bind mount capabilities to dramatically improve CI build times and reduce image sizes. Instead of copying source files into intermediate layers, use bind mounts to provide build context and cache mounts for package managers and build artifacts.","repository":"astral-sh/uv","domain":"devtools","topic":"CI/CD","language":"Dockerfile","updated":"2025-04-29","comments":2,"stars":60322,"raw":"https://awesomereviewers.com/raw/uv-optimize-docker-build-caching.md"},{"slug":"volcano-use-latest-patch-versions","title":"Use latest patch versions","description":"When configuring dependencies in Dockerfiles and other configuration files, use the latest patch versions while keeping major and minor versions fixed. Patch versions typically contain important security fixes and bug corrections without introducing breaking changes. For example, prefer `golang:1.23.7` over `golang:1.23.0`, as \"small versions will fix some...","repository":"volcano-sh/volcano","domain":"orchestration","topic":"Configurations","language":"Dockerfile","updated":"2025-03-21","comments":2,"stars":4899,"raw":"https://awesomereviewers.com/raw/volcano-use-latest-patch-versions.md"},{"slug":"ollama-keep-container-images-current","title":"Keep container images current","description":"Always use up-to-date and supported container images in Dockerfiles and configuration files. Before specifying a base image or version: 1. Verify the image hasn''t been deprecated","repository":"ollama/ollama","domain":"llm-infra","topic":"Configurations","language":"Dockerfile","updated":"2025-02-09","comments":2,"stars":145705,"raw":"https://awesomereviewers.com/raw/ollama-keep-container-images-current.md"},{"slug":"unstructured-parameterize-hardcoded-configuration-values","title":"Parameterize hardcoded configuration values","description":"Replace hardcoded values in configuration files with parameterized variables to improve flexibility and maintainability. Use build arguments (ARG) and environment variables (ENV) in Dockerfiles instead of embedding specific versions, paths, or other configuration values directly in the code.","repository":"Unstructured-IO/unstructured","domain":"llm-infra","topic":"Configurations","language":"Dockerfile","updated":"2025-01-06","comments":2,"stars":12117,"raw":"https://awesomereviewers.com/raw/unstructured-parameterize-hardcoded-configuration-values.md"}],"prompt_count":17},{"slug":"dependencies","title":"Dependencies and lockfiles","topics":[],"checks":[{"kind":"dependency-audit","title":"Dependency audit","method":"supply_chain","method_slug":"supply-chain","catches":"Known-vulnerable or disallowed dependencies and licenses.","tool":null,"alternatives":[],"note":null},{"kind":"lockfile-check","title":"Lockfile consistency","method":"supply_chain","method_slug":"supply-chain","catches":"A lockfile that no longer matches its manifest.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":null,"alternatives":[],"note":null}],"prompts":[],"prompt_count":0},{"slug":"tests","title":"The tests themselves","topics":["Testing"],"checks":[{"kind":"mutation-testing","title":"Mutation testing","method":"testing","method_slug":"testing","catches":"Tests that keep passing whatever the code does.","tool":null,"alternatives":[],"note":null},{"kind":"version-matrix","title":"Version and platform matrix","method":"testing","method_slug":"testing","catches":"Breakage on a runtime version, OS or feature combination you did not run locally.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"browser-use-pin-testing-dependency-versions","title":"Pin testing dependency versions","description":"Always specify explicit versions for testing frameworks and tools to ensure reproducible test environments across different deployment contexts. Avoid installing testing dependencies with implicit \"latest\" versions, which can lead to inconsistent test behavior and difficult-to-debug failures.","repository":"browser-use/browser-use","domain":"ai-agents","topic":"Testing","language":"Dockerfile","updated":"2025-05-13","comments":3,"stars":69139,"raw":"https://awesomereviewers.com/raw/browser-use-pin-testing-dependency-versions.md"}],"prompt_count":1},{"slug":"docs","title":"Documentation and comments","topics":["Documentation"],"checks":[{"kind":"docs-build","title":"Docs build","method":"static_analysis","method_slug":"static-analysis","catches":"Broken cross-references, links and markup in documentation.","tool":null,"alternatives":[],"note":null},{"kind":"spelling","title":"Spelling","method":"formatting","method_slug":"formatting","catches":"Typos in identifiers, comments and docs.","tool":null,"alternatives":[],"note":null}],"prompts":[{"slug":"kubeflow-document-with-precision","title":"Document with precision","description":"Write informative, consistent, and precise code comments throughout your codebase. When documenting code: 1. **Be specific with references** - When referencing external repositories or sources, link to specific versions and files, not just directories. Use precise language to describe the relationship between your code and external sources.","repository":"kubeflow/kubeflow","domain":"ml-systems","topic":"Documentation","language":"Dockerfile","updated":"2024-08-17","comments":3,"stars":15064,"raw":"https://awesomereviewers.com/raw/kubeflow-document-with-precision.md"}],"prompt_count":1}]}