Old docker_aio AppAPI daemon remains registered after AIO 12.9.1 Beta migration from Docker Proxy to HaRP

[vawaver]

Hi,

I would like to report a migration issue I ran into after updating to Nextcloud AIO 12.9.1 Beta on the Beta channel, where I switched from Docker Proxy for ExApps to HaRP.

Problem

After the update, the old AppAPI daemon docker_aio was still registered and pointing to:

nextcloud-aio-docker-socket-proxy:2375

At the same time:

• the old Docker Socket Proxy was no longer usable
• ExApps were no longer manageable from the GUI
• the system ended up in a half-migrated state until I cleaned it up manually

Symptoms

From the user perspective, I saw:

• Deploy and Enable inactive for affected ExApps
• Docker Proxy shown as unavailable
• old ExApp containers still present in Docker
• GUI unable to disable, redeploy, or recover the apps properly

From OCC:

sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ app_api:daemon:list

showed the old daemon still registered.

What I had to do manually

I had to unregister the old daemon manually with:

sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ app_api:daemon:unregister docker_aio

Only after that could I continue with the HaRP recovery path.

Expected behavior

When AIO switches from Docker Proxy to HaRP, I would expect the old docker_aio daemon to be handled automatically, or at least cleaned up in a way that does not leave the user in a broken in-between state.

Actual behavior

The old daemon remained registered and still pointed to the removed/unavailable Docker Socket Proxy, which contributed to the migration getting stuck until manual intervention.

Environment

• Nextcloud AIO 12.9.1 Beta
• Beta channel
• migration from Docker Proxy for ExApps to HaRP

[szaimen]

Hi, so I checked this and I fear it is not really possible to run sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ app_api:daemon:unregister docker_aio automatically. We would need to manually clean up the linked containers first. However I'd say this needs to be done by the admin manually beforehand. So doing things like mentioned in https://help.nextcloud.com/t/aio-12-9-1-beta-harp-migration-old-exapps-left-behind-gui-stuck-manual-recovery-steps/242826 is probably the best way to do it.