Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

python3 fails with "Operation not permitted" (exit 126) on arm64 (Raspberry Pi 5) — confirmed not host-related

Open
  • Is something wrong?
#1,694 11 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, linux, python
Domain
backend, infrastructure

Research direction

Start by reading the container startup path at /entrypoint.d/15-mounts.py and examining how the image bundles and invokes python3; compare its behavior on arm64 with the reported working Python images. The issue provides extensive environment checks but no reproduction steps or logs, so first establish a reproducible test. Done means the NetAlertX container starts successfully on the Raspberry Pi 5 without the permission error.

Written by the indexing model from the issue text.

Description

bug 🐛 help wanted 🆘 Waiting for reply⏳
What installation are you running?

Production (netalertx) 📦

Is there an existing issue for this?
The issue occurs in the following browsers. Select at least 2.
  • Firefox
  • Chrome
  • Edge
  • Safari (unsupported) - PRs welcome
  • N/A - This is an issue with the backend
Current Behavior

Environment: Raspberry Pi 5, Debian 12 (Bookworm), aarch64, Docker 29.6.1, containerd 2.2.5, runc 1.3.6, overlay2/extfs storage
Issue: Container fails at /entrypoint.d/15-mounts.py with env: can't execute 'python3': Operation not permitted, on both :latest and :26.3.7.
Ruled out (with evidence):

Privilege drop / PUID — fails identically running fully as root (PUID=0)
AppArmor — disabled at kernel level (aa-status: not mounted)
Seccomp — fails identically with --security-opt seccomp=unconfined
Rootless Docker — confirmed standard rootful daemon, cgroup v2/systemd
Docker storage — overlay2/extfs, no noexec, confirmed via findmnt
binfmt_misc — disabled the host's python3.11 handler, no change
systemd hardening on docker/containerd — fully open (no NoNewPrivileges, full CapabilityBoundingSet)
Host-wide exec — ruled out entirely: python:3.12-slim and alpine:latest both run perfectly on the same host

Conclusion: appears isolated to the netalertx image's bundled Python binary/build itself.

Expected Behavior

not failing to start

Steps To Reproduce

No response

Relevant app.conf settings
docker-compose.yml
Debug or Trace enabled
  • I have read and followed the steps in the wiki link above and provided the required debug logs and the log section covers the time when the issue occurs.
Relevant app.log section
  PASTE LOG HERE. Using the triple backticks preserves format.
Docker Logs
  PASTE DOCKER LOG HERE. Using the triple backticks preserves format.
Dominant language
Python
Stars
7.2k
Forks
456
Avg merge
16h 25m
Merged PRs (30d)
30

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from netalertx/NetAlertX

All issues in netalertx/NetAlertX

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.