A container has its own network environment. Publishing a port connects a host listener to a container port using host:container order. Environment variables configure a container when you create it. The host shell and the container have separate environments; exporting a value on the host doesn't automatically pass it through. The writable layer belongs to one container. A named volume has a separate lifecycle, which lets data survive container replacement.
Apply those boundaries to fresh fixtures. Inspect the requested name, namespace, path and value before reusing a command. The tasks mix earlier operations and include nearby wrong targets, so preserve unrelated work. Choose any supported approach that produces the complete requested state; the checker evaluates the result rather than a recorded command sequence.