I had noticed that temporary container it created (and never deletes, BTW, so you’ll want to clean that up) but hadn’t thought to look at the logs. I’m seeing basically the exact same thing.

2023/11/27 10:21AM INF portainer/portainer.go:76 > Updating Portainer on standalone environment | image=portainer/portainer-ee:latest 
2023/11/27 10:21AM INF dockerstandalone/update.go:28 > Starting update process | containerId=ef7fd725b19df3e07708d0a88ed1d5d2a699ea2707d78aae9ad99c44938162f7 image=portainer/portainer-ee:latest status=Pulling from portainer/portainer-ee id=latest status=Digest: sha256:0140cf5751b61d07bcd9b48a800f6e178bb114267d5d2be7c5f4770222651677 status=Status: Image is up to date for portainer/portainer-ee:latest 2023/11/27 10:21AM INF dockerstandalone/update.go:62 > Image is already up to date, shutting down | image=portainer/portainer-ee:latest containerId=ef7fd725b19df3e07708d0a88ed1d5d2a699ea2707d78aae9ad99c44938162f7