The initContainer for jobs.preRegisterContentCommand did not get some of the updates applied to the primary register-content command container. That may be the source of (part of) the issue reported in #320. Whether or not this fixes that issue, the mounts still need to be fixed / synchronized with the primary mounts.

Sadly, testing initContainers with helm-unittest is going to be extremely difficult because it requires assertions using the exact index of the container. When helm-unittest adds support for looking up an object in an array using a key, like name, then we can add tests for initContainers. Until then, we just have to do our best to keep the initContainers synchronized as needed.