Greetings @cifengfang,
The issue you’re experiencing here sounds like what happened on this thread here: Offline Docker Compose updates do not tag images properly, docker-compose fails after successful update
Ultimately the issue is due to a bug with Docker where the “incorrect” container image gets pruned sometimes. But, just to make sure it really is the same issue, can you describe to me your exact process leading up to this.
If I understand your general process it went something like:
- You started with a TorizonCore image that had your containers pre-loaded correct?
- Then you performed an offline update to update just the containers.
Did I get the general idea?
If yes, then I have further questions:
- What is the exact process you did to produce the TorizonCore image with your containers pre-loaded?
- After booting this TorizonCore image with your containers pre-loaded what is the output of
docker imageson your system? - The offline update you were applying, were all 3 containers being changed in the update? Or were some going to stay the same?
- After the failed offline update what is the output of
docker imageson your system?
Best Regards,
Jeremias