> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/engines/install-an-engine/docker/docker-faqs.md). # Docker FAQs * **Does Cortex Cloud use COPY or ADD for building images?** Cortex Cloud uses COPY for building images. The COPY instruction copies files from the local host machine to the container file system. Cortex Cloud does not use the ADD instruction, which could potentially retrieve files from remote URLs and perform operations such as unpacking, introducing potential security vulnerabilities. * **Should the `--restart flag` be used?** The --restart flag should not be used. Cortex Cloud manages the lifecycle of Docker images and restarts images as needed. * **Can we restrict containers from acquiring additional privileges by setting the no-new-privileges option?** Cortex Cloud does not support the no-new-privileges option. Some integrations and scripts may need to change privileges when running as a non-root user (such as Ping). * **Can we apply a daemon-wide custom seccomp profile?** The [default seccomp profile](https://docs.docker.com/engine/security/seccomp/) from Docker is strongly recommended. The default seccomp profile provides protection as well as wide application compatibility. While you can apply a custom seccomp profile, Cortex Cloud cannot guarantee that it won't block system calls used by an integration or script. If you apply a custom seccomp profile, you need to verify and test the profile with any integrations or scripts you plan to use. * **Can we use TLS authentication for docker daemon configuration?** TLS authentication is not used, because Cortex Cloud does not use Docker remote connections. All communication is done via the local Docker IPC socket. * **How do we set the logging level to** **`info`**? Set the log level in the [Docker daemon configuration file](https://docs.docker.com/engine/reference/commandline/dockerd/#daemon-configuration-file). * **Can we restrict Linux kernel capabilities within containers?** The default Docker settings (recommended) include 14 kernel capabilities and exclude 23 kernel capabilities. Refer to Docker’s [full list of runtime privileges and Linux capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities). You can further exclude capabilities via advanced configuration, but will first need to verify that you are not using a script that requires the capability. For example, Ping requires **`NET_RAW`** capability. * **Is the Docker health check option implemented at runtime?** The Cortex Cloud tenant monitors the health of the containers and restarts/terminates containers as needed. The Docker health check option is not needed. * **Can we enable live restore?** Live restore is not used. Cortex Cloud uses ephemeral Docker containers. Every running container is stateless by design. * **Can we restrict network traffic between containers?** Cortex Cloud does not disable inter-container communication by default, as there are use cases where this might be needed. For example, a script communicating with a long running integration which listens on a port, may require inter-container communication. If inter-container communication is not required, it can be disabled by modifying the [Docker daemon configuration.](https://docs.docker.com/engine/reference/commandline/dockerd/) * **Can we enable user namespace remapping?** Cortex Cloud does not support user namespace remapping. * **How do we configure auditing for Docker files and directories?** Auditing is an operating system configuration, and can be enabled in the operating system settings. Cortex Cloud does not change the audit settings of the operating system. * **Can we disable the userland proxy?** If the kernel supports hairpin NAT, you can disable docker userland proxy settings by modifying the [Docker daemon configuration](https://docs.docker.com/engine/reference/commandline/dockerd/). * **Does Cortex Cloud support the AppArmor profile?** Cortex Cloud supports the default AppArmor profile (only relevant for Ubuntu with AppArmor enabled). * **Does Cortex Cloud support the SELinux profile?** Cortex Cloud supports the default SELinux profile (only relevant for RedHat with SELinux enabled). * **How does Cortex Cloud handle secrets management?** For Docker swarm services, a secret is a blob of data, such as password, SSH private keys, SSL certificates, or other piece of data that should not be transmitted over a network or stored unencrypted in a Docker file or in your application’s source code. Cortex Cloud manages integration credentials internally. It also supports using an [external credentials service](https://xsoar.pan.dev/docs/reference/articles/managing-credentials) such as CyberArk. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/investigation-and-response/automation/engines/install-an-engine/docker/docker-faqs.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.