Capabilities are a Linux kernel feature that allows processes to perform some privileged operations without having the full power of the root user1. Docker uses capabilities to limit the access of containers to host resources, such as CPU or memory2. By default, Docker drops all capabilities except those needed for the container to function properly, using a whitelist approach3. This reduces the risk of a container compromising the host system or other containers. You can also add or remove capabilities to or from a container at runtime, using the --cap-add or --cap-drop options of the docker run command4. This gives you more control over the security and functionality of your containers. References:
* Capabilities | dockerlabs
* Docker run reference | Docker Docs
* Docker Capabilities and no-new-privileges
* Runtime privilege and Linux capabilities | Docker Docs

Explanation
An instance of the Docker CLI connected to the swarm does not describe a node in the context of a swarm mode cluster. A node is a physical or virtual machine that runs the Docker Engine and participates in the swarm. A node can have one of two roles: manager or worker. Manager nodes maintain the cluster state and orchestrate tasks. Worker nodes execute tasks assigned by manager nodes. An instance of the Docker CLI connected to the swarm is a client that can interact with the swarm using commands such as docker service, docker node, docker stack, etc. A client can connect to any manager node in the swarm using the --host or -H flag. References: https://docs.docker.com/engine/swarm/key-concepts/#nodes-and-services,
https://docs.docker.com/engine/swarm/swarm-tutorial/#use-docker-for-mac-or-docker-for-windows

Explanation
Inter-process communication is not blocking this operation. Inter-process communication (IPC) is a mechanism that allows processes to communicate and synchronize their actions. IPC creates a set of interfaces for exchanging various types of data. Docker supports IPC namespaces to isolate IPC resources between processes in different containers. However, IPC does not affect the ability to set the system time from inside a Docker container. References: https://docs.docker.com/engine/reference/run/#ipc-settings-ipc,
https://man7.org/linux/man-pages/man7/ipc.7.html

Explanation
Using kubectl describe deployment api displays the events table for this object. The kubectl describe command shows detailed information about a resource, including its status and events. This command can be used to troubleshoot a deployment that is not working as expected. References:
https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#describe

https://docs.docker.com/engine/reference/commandline/swarm/