nextcloud / nextcloud/notify_push

Did not find a matching notify-push binary for your cpu arch: aarch64

Open
#650 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Rust
Stars
344
Forks
64
Avg merge
2d 10h
Merged PRs (30d)
5

Description

I updated to the latest linuxserver nextcloud container and now have the following in my log:

[mod-init] Running Docker Modification Logic
[mod-init] Adding linuxserver/mods:nextcloud-notify-push to container
[mod-init] linuxserver/mods:nextcloud-notify-push at sha256:2b769e5d440cd0c4e01c27006722a7d64c64ef819d41918b6a226f03c320e417 has been previously applied skipping
[migrations] started
[migrations] 01-nginx-site-confs-default: skipped
[migrations] 02-default-location: skipped
[migrations] done
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 31.0.8-ls391
Build-date: 2025-08-19T11:53:15+00:00
───────────────────────────────────────
    
using keys found in /config/keys
[custom-init] No custom files found, skipping...
**** Making sure the Nextcloud Client Push plugin is installed and enabled ****
notify_push already installed
notify_push already enabled
**** Did not find a matching notify-push binary for your cpu arch: aarch64 ****

I am running it on a Mac Mini M4 and previously it was fine.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the linuxserver Nextcloud container on an aarch64 host and inspect how the notify-push binary is selected and installed. Compare the available binary architecture with the container's reported aarch64 CPU; done means the notify-push plugin starts without the missing-binary warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, rust
Domain
infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.