Sorry, I forgot to check back in. Yes, that was the error we were observing. We have never seen that before. The error went away as soon as we forced the container to stop and the orchestrator started a new container the problem went away.