I’m guessing this because of the ongoing AWS issues, but I just tried updating an iX App (file browser) and it failed with the following output:
[2025/10/20 09:57:27] (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'filebrowser' app: init Pulling \n filebrowser Pulling \n filebrowser Error Head "https://registry-1.docker.io/v2/filebrowser/filebrowser/manifests/v2.44.1": received unexpected HTTP status: 503 Service Unavailable\n init Error context canceled\nError response from daemon: Head "https://registry-1.docker.io/v2/filebrowser/filebrowser/manifests/v2.44.1": received unexpected HTTP status: 503 Service Unavailable\n
Unfortunately, I can’t now start it as it appears to delete the container before it (fails to) download the new one.
I tried rolling back to the previous version, but it says you can’t rollback a container that isn’t running. And as I can’t run it… 
Fortunately this isn’t a mission critical app for me, but I figured others may get caught out with more important services if they didn’t know.