I also have this problem on 6.12.4 and it seems to affect random containers. I don't see any difference based on what network the container uses or actual update availability.
Search has turned up very few mentions of this problem since 6.12.0 became available. Only solution I've found personally is to delete each affected container when this happens and reinstall. Has anyone found a better solution?