-
Notifications
You must be signed in to change notification settings - Fork 15
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
After updating to Docker 29 deployment daemons no longer work for NC via HaRP or docker-socket-proxy. This is due to the well known API changes which have now been raised to 1.44 - NC uses 1.41
Errors:
Socket Proxy:
ClientException Client error:GET http://dockerproxy:2375/v1.41/_ping` resulted in a 400 Bad Request response: {"message":"client version 1.41 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer (truncated...)
Could not connect to Docker daemon via http://dockerproxy:2375/v1.41/_ping `
HaRP:
Deploy daemon "harp_proxy_docker" is not accessible by Nextcloud. Please verify its configuration
Steps to reproduce
- Go to /settings/admin/app_api
- Set up docker-socket-proxy or HaRP proxy
- Check /admin/logging
Expected behavior
Expect the Ex_Apps deployment to work but it doesn't due to logged failure.
Nextcloud Server version
32
Operating system
Debian/Ubuntu
PHP engine version
None
Web server
None
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response