fix(docker): add HEALTHCHECK NONE to Dockerfile#31
fix(docker): add HEALTHCHECK NONE to Dockerfile#31google-labs-jules[bot] wants to merge 1 commit into
Conversation
…or docker image runs a short-lived CLI tool as its entrypoint, not a long-running daemon. Added `HEALTHCHECK NONE` to explicitly signal this and suppress the `docker-no-healthcheck` finding in security scans.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This PR addresses the
docker-no-healthcheckfinding from thewebsectool's self-scan. \n\nWhat: AppendsHEALTHCHECK NONEto theDockerfile.\nWhy: The container is meant for executing a short-lived, transient CLI command (websec run ...) and not a long-running daemon, so a health check is intentionally not applicable here.\nRisk: Very low. It suppresses noise in container linting/scanning and does not modify any application logic.PR created automatically by Jules for task 9195613552503831721 started by @raccioly