Explanation
This set of commands can identify the published port(s) for a container. The docker container inspect command shows low-level information about a container in JSON format. This information includes the network settings of the container, such as the port bindings and exposed ports. The docker port command shows the public port(s) that are mapped to a private port inside the container. By using these two commands, you can identify the published port(s) for a container. References:
https://docs.docker.com/engine/reference/commandline/container_inspect/,
https://docs.docker.com/engine/reference/commandline/port/

Explanation
Docker blocks this command if you configure a local Docker engine to enforce content trust by setting the environment variable DOCKER_CONTENT_TRUST=1 and if myorg/myimage:1.0 is unsigned. Content trust is a feature that allows you to use digital signatures to verify the integrity and publisher of specific image tags.
When you enable content trust, you can only pull, run, or build with trusted images. If an image tag is unsigned, Docker will block any command that attempts to use it. This includes docker image build, from a Dockerfile that begins FROM myorg/myimage:1.0, if myorg/myimage:1.0 is unsigned. References:
https://docs.docker.com/engine/security/trust/,
https://docs.docker.com/engine/reference/commandline/image_build/

Explanation
This command will display a list of volumes for a specific container, because it uses docker container inspect to show detailed information about a container, including its volumes. According to the official documentation, docker container inspect will show the Mounts section that contains information about all volumes mounted by the container.
References: https://docs.docker.com/engine/reference/commandline/container_inspect/
https://docs.docker.com/storage/volumes/#start-a-container-with-a-volume

Explanation
SAML is a supported user authentication method for Universal Control Plane (UCP). SAML (Security Assertion Markup Language) is an open standard for exchanging authentication and authorization data between parties, such as an identity provider and a service provider. UCP supports SAML as an external authentication backend, which allows users to log in to UCP using their existing credentials from a SAML identity provider, such as Okta, Ping Identity, OneLogin, etc. UCP also supports other external authentication backends, such as LDAP and Active Directory. References:
https://docs.docker.com/ee/ucp/admin/configure/external-auth/,
https://docs.docker.com/ee/ucp/admin/configure/saml/

Explanation
The PVC remains unbound until a persistentVolume that matches all requirements of the PVC becomes available is an action Kubernetes takes in this situation. A persistentVolumeClaim (PVC) is a request for storage by a user. A PVC specifies the desired size, access modes, and storage class of the storage. A persistentVolume (PV) is a piece of storage in the cluster that has been provisioned by an administrator. A PV has a lifecycle independent of any individual pod that uses it. A PVC is automatically bound to a suitable PV based on its requirements. If no PV exists that matches the PVC, and dynamic provisioning is not enabled, then the PVC remains unbound indefinitely until a matching PV is created. References:
https://kubernetes.io/docs/concepts/storage/persistent-volumes/,
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#lifecycle-of-a-volume-and-claim