hermes - 💡(How to fix) Fix [Setup]: Docker build fails on QNAP NAS: s6-overlay "Cannot change mode" Bad address

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Full Error Output

Fix Action

Fix / Workaround

Workaround The previous version (v0.14.0) used tini as the process manager, which builds and runs perfectly on QNAP NAS.

Code Example



---

tar: ./package/admin/s6-overlay: Cannot change mode to rwxrwxrwx: Bad address
tar: ./command/printcontenv: Cannot change mode to rwxrwxrwx: Bad address
tar: Exiting with failure status due to previous errors
This happens with both tar -Jxpf (preserve permissions) and tar -Jxf (without -p). The QNAP kernel's filesystem driver does not support the chmod operations that s6-overlay's tar archive requires during extraction.
RAW_BUFFERClick to expand / collapse

What's Going Wrong?

Environment Device: QNAP NAS OS: QTS (Linux kernel with QNAP's ext4/f2fs driver) Docker: Docker via Container Station Architecture: amd64 Problem Starting from the version that introduced s6-overlay, Docker build fails with Bad address errors when tar extracts s6-overlay archives:

tar: ./package/admin/s6-overlay: Cannot change mode to rwxrwxrwx: Bad address tar: ./command/printcontenv: Cannot change mode to rwxrwxrwx: Bad address tar: Exiting with failure status due to previous errors This happens with both tar -Jxpf (preserve permissions) and tar -Jxf (without -p). The QNAP kernel's filesystem driver does not support the chmod operations that s6-overlay's tar archive requires during extraction.

Workaround The previous version (v0.14.0) used tini as the process manager, which builds and runs perfectly on QNAP NAS.

Request Please consider providing a Dockerfile variant (e.g., Dockerfile.tini) that uses tini instead of s6-overlay, or add a build arg to skip s6-overlay installation. QNAP NAS devices are commonly used as self-hosted servers and would benefit from continued compatibility.

Related This is similar to the chmod -R a+rX issue on QNAP (also "Bad address"), which was previously worked around by using targeted chmod +x on specific files instead of recursive chmod.

Steps Taken

  1. has download the hermes agent zip package
  2. unzip and then using docker build
  3. cannot install due to above mentioned problem

Installation Method

Docker

Operating System

OS: QTS (Linux kernel with QNAP's ext4/f2fs driver)

Python Version

No response

Hermes Version

No response

Debug Report

Full Error Output

tar: ./package/admin/s6-overlay: Cannot change mode to rwxrwxrwx: Bad address
tar: ./command/printcontenv: Cannot change mode to rwxrwxrwx: Bad address
tar: Exiting with failure status due to previous errors
This happens with both tar -Jxpf (preserve permissions) and tar -Jxf (without -p). The QNAP kernel's filesystem driver does not support the chmod operations that s6-overlay's tar archive requires during extraction.

What I've Already Tried

No response

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Setup]: Docker build fails on QNAP NAS: s6-overlay "Cannot change mode" Bad address