Generate dockerfile documentation after updating SecretsUsedInArgOrEnv rule description

Signed-off-by: Talon Bowler <[email protected]>

Author: daghack

frontend/dockerfile/docs/rules/_index.md

@@ -86,7 +86,7 @@ $ docker build --check .
     </tr>
     <tr>
       <td><a href="./secrets-used-in-arg-or-env/">SecretsUsedInArgOrEnv</a></td>
-      <td>Potentially sensitive data should not be used in the ARG or ENV commands</td>
+      <td>Sensitive data should not be used in the ARG or ENV commands</td>
     </tr>
   </tbody>
 </table>

frontend/dockerfile/docs/rules/secrets-used-in-arg-or-env.md

@@ -1,6 +1,6 @@
 ---
 title: SecretsUsedInArgOrEnv
-description: Potentially sensitive data should not be used in the ARG or ENV commands
+description: Sensitive data should not be used in the ARG or ENV commands
 aliases:
   - /go/dockerfile/rule/secrets-used-in-arg-or-env/
 ---

frontend/dockerfile/linter/docs/SecretsUsedInArgOrEnv.md

@@ -6,13 +6,17 @@ Potentially sensitive data should not be used in the ARG or ENV commands
 
 ## Description
 
-While it is common in many local development setups to pass secrets to running
-processes through environment variables, setting these within a Dockerfile via
-the `ENV` command means that these secrets will be committed to the build
-history of the resulting image, exposing the secret. For the same reasons,
-passing secrets in as build arguments, via the `ARG` command, will similarly
-expose the secret. This rule reports violations where `ENV` and `ARG` key names
-appear to be secret-related.
+While it is common to pass secrets to running processes
+through environment variables during local development,
+setting secrets in a Dockerfile using `ENV` or `ARG`
+is insecure because they persist in the final image.
+This rule reports violations where `ENV` and `ARG` keys
+indicate that they contain sensitive data.
+
+Instead of `ARG` or `ENV`, you should use secret mounts,
+which expose secrets to your builds in a secure manner,
+and do not persist in the final image or its metadata.
+See [Build secrets](https://docs.docker.com/build/building/secrets/).
 
 ## Examples