Skip to content

[Bug]: AppApi deployment no longer works with Docker 29 #712

Closed

Description

@rageebm

⚠️ This issue respects the following points: ⚠️

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

  1. Go to /settings/admin/app_api
  2. Set up docker-socket-proxy or HaRP proxy
  3. 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

Activity

  1. added theissue type on Nov 22, 2025
  2. demiant165 commented on Nov 23, 2025

    @demiant165

    I'll add the error, nothing was deployed normally, the error is below and just points to the api, so it made sense to roll out an update where the code was not normally messed up.
    Client error: GET http://localhost:8780/exapps/app_api/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...)`

  3. Tail870 commented on Nov 23, 2025

    @Tail870

    Having same issue with "client is too old".

  4. Tail870 commented on Nov 24, 2025

    @Tail870

    @rageebm, @demiant165, you can add "min-api-version" into daemon.json to ease API version requirements.
    Here's my config for example:

    cat /etc/docker/daemon.json 
    {
      "storage-driver": "fuse-overlayfs",
      "min-api-version": "1.41"
    }
    
  5. oleksandr-nc commented on Nov 24, 2025

    @oleksandr-nc
    Contributor

    Hello, this a duplicate of this:

    #709
    nextcloud/HaRP#69

    Problem will be fixed in the next release of Nextcloud

  6. rageebm commented on Nov 24, 2025

    @rageebm
    Author

    @rageebm, @demiant165, you can add "min-api-version" into daemon.json to ease API version requirements. Here's my config for example:

    cat /etc/docker/daemon.json 
    {
      "storage-driver": "fuse-overlayfs",
      "min-api-version": "1.41"
    }
    

    Hey,
    Thank you. Yes - the same workaround works for Portainer and other effected apps also

  7. oleksandr-nc commented on Apr 21, 2026

    @oleksandr-nc
    Contributor

    Closing as resolved.

    #797 made the version configurable via appConfig, so if someone ever need to pin a different version , you can override it without a code change:

    occ config:app:set app_api docker_api_version --value v1.44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions