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 network attach to access the containers on the bridge network does not make the container reachable from its host's network. The network attach option connects a running container to another network, but it does not expose any ports to the host. To make a container reachable from its host's network, you need to use either EXPOSE or --publish to access the containers on the bridge network. References:
https://docs.docker.com/engine/reference/commandline/network_connect/,
https://docs.docker.com/config/containers/container-networking/

Explanation
This does not configure a Docker container to export container logs to the logging solution. The docker logs command shows information about the logs of a container. It does not export or send the logs to any external destination. To configure a Docker container to export container logs to the logging solution, you need to use the --log-driver and --log-opt flags when creating or running the container. These flags allow you to specify which logging driver and options to use for the container. For example, to use Splunk as the logging driver, you can use --log-driver splunk and provide the Splunk URL, token, and other options using --log-opt.
References: https://docs.docker.com/engine/reference/commandline/logs/,
https://docs.docker.com/config/containers/logging/configure/,
https://docs.docker.com/config/containers/logging/splunk/

Explanation
Linux capabilities are blocking this operation. Linux capabilities are a partitioning of the privileges traditionally associated with superuser into distinct units, known as capabilities, which can be independently enabled and disabled. Capabilities are used by Docker to restrict the operations that a container can perform on the host system. By default, Docker drops all capabilities except those needed for common operations, such as binding to ports below 1024 or mounting filesystems. One of the capabilities that is dropped by default is CAP_SYS_TIME, which allows setting the system clock. Therefore, a user cannot set the system time from inside a Docker container unless this capability is explicitly added. References:
https://docs.docker.com/engine/security/security/#linux-kernel-capabilities,
https://man7.org/linux/man-pages/man7/capabilities.7.html

Explanation
= Control Groups (cgroups) are a feature of the Linux kernel that allow you to limit the access processes and containers have to system resources such as CPU, memory, disk I/O, network, and so on1. Control groups allow Docker Engine to share available hardware resources to containers and optionally enforce limits and constraints2. For example, you can use the docker run command to specify the CPU shares, memory limit, or network bandwidth for a container3. By using cgroups, you can ensure that each container gets the resources it needs and prevent resource starvation or overcommitment4. References:
* Lab: Control Groups (cgroups) | dockerlabs
* Runtime metrics | Docker Docs
* Docker run reference | Docker Docs
* Docker resource management via Cgroups and systemd