Explanation
Using seccomp does not limit a Docker container's access to host resources, such as CPU or memory.
Seccomp is a Linux kernel facility that allows filtering system calls made by a process. It can be used to enhance the security and isolation of a container by restricting its access to certain system calls. However, it does not affect the resource allocation or consumption of a container. References:
https://docs.docker.com/engine/security/seccomp/,
https://www.kernel.org/doc/html/v4.14/userspace-api/seccomp_filter.html

Explanation
This command will not display a list of volumes for a specific container, because it has several syntax errors and invalid options. According to the official documentation, there is no such command as docker volume logs or such option as --containers.
References: https://docs.docker.com/engine/reference/commandline/volume/

Explanation
This command does not mount the host's /data directory to the ubuntu container in read-only mode. The -v or
--volume flag mounts a host directory or a named volume to a container. The syntax for mounting a host directory is -v <host-path>:<container-path>[:<options>]. The options can be ro for read-only mode, rw for read-write mode, z or Z for SELinux labels, etc. In this command, -mode readonly is not a valid option and will cause an error. To mount the host's /data directory to the ubuntu container in read-only mode, you need to use -v /data:/mydata:ro instead. References: https://docs.docker.com/storage/bind-mounts/,
https://docs.docker.com/engine/reference/run/#volume-shared-filesystems