starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[GH-ISSUE #11857] Omada helper fails on Debian 12: Adoptium repo missing GPG key (NO_PUBKEY 843C48A565F8F04B) #2494

New issue

Closed

opened 2026-02-26 12:52:38 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 12:52:38 +03:00

Owner

Originally created by @DrewSweeney33 on GitHub (Feb 12, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11857

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

No response

📜 What is the name of the script you are using?

Omada

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

9.1.4

📝 Provide a clear and concise description of the issue.

When running ct/omada.sh, the build fails at apt update with:
NO_PUBKEY 843C48A565F8F04B
Repository: https://packages.adoptium.net/artifactory/deb
bookworm InRelease

The repo is created as /etc/apt/sources.list.d/adoptium.sources (deb822), so cleanup of *.list does not remove it. The script appears to run apt update before importing the Adoptium public key and configuring signed-by in /etc/apt/keyrings.

Suggested fix:
Import Adoptium key first (gpg dearmor to /etc/apt/keyrings/adoptium.gpg), then add repo using signed-by, then run apt update. Also handle .sources format.

🔄 Steps to reproduce the issue.

Run the script and use either advanced settings or default settings: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)"

❌ Paste the full error output (if available).

✖️ in line 1337: exit code 100 (APT: Package manager error (broken packages / dependency problems))
→ apt update
--- Last 10 lines of silent log ---

Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://security.debian.org bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Get:4 https://packages.adoptium.net/artifactory/deb bookworm InRelease [7,507 B]
Err:4 https://packages.adoptium.net/artifactory/deb bookworm InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 843C48A565F8F04B
Reading package lists...
W: GPG error: https://packages.adoptium.net/artifactory/deb bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 843C48A565F8F04B
E: The repository 'https://packages.adoptium.net/artifactory/deb bookworm InRelease' is not signed.

📋 View full log (443 lines): /root/.install-1d23d771.log
✖️ Installation failed in container 115 (exit code: 100)

✔ Installation log: /tmp/install-lxc-115-1d23d771.log

Remove broken container 115? (Y/n) [auto-remove in 60s]: n

Container 115 kept for debugging
root@pvemain:~#

🖼️ Additional context (optional).

Script: Omada Controller (ct/omada.sh)

Proxmox: 9.1.4, Debian 12, unprivileged LXC

Exact failure: apt update fails on Adoptium repo key

Error: NO_PUBKEY 843C48A565F8F04B, repository not signed

Root cause: script adds Adoptium repo and runs apt update before importing the repo key, and it uses a deb822 .sources file (adoptium.sources) so wildcard delete of *.list does not remove it

Fix request: import Adoptium key and write it to /etc/apt/keyrings before adding the repo and before any apt update, also handle .sources files

Optional improvement: force APT to IPv4 if container has no IPv6, or document it

Originally created by @DrewSweeney33 on GitHub (Feb 12, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11857 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? _No response_ ### 📜 What is the name of the script you are using? Omada ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? 9.1.4 ### 📝 Provide a clear and concise description of the issue. When running ct/omada.sh, the build fails at apt update with: NO_PUBKEY 843C48A565F8F04B Repository: https://packages.adoptium.net/artifactory/deb bookworm InRelease The repo is created as /etc/apt/sources.list.d/adoptium.sources (deb822), so cleanup of *.list does not remove it. The script appears to run apt update before importing the Adoptium public key and configuring signed-by in /etc/apt/keyrings. Suggested fix: Import Adoptium key first (gpg dearmor to /etc/apt/keyrings/adoptium.gpg), then add repo using signed-by, then run apt update. Also handle .sources format. ### 🔄 Steps to reproduce the issue. Run the script and use either advanced settings or default settings: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh)" ### ❌ Paste the full error output (if available). ✖️ in line 1337: exit code 100 (APT: Package manager error (broken packages / dependency problems)) → apt update --- Last 10 lines of silent log --- Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://security.debian.org bookworm-security InRelease Hit:3 http://deb.debian.org/debian bookworm-updates InRelease Get:4 https://packages.adoptium.net/artifactory/deb bookworm InRelease [7,507 B] Err:4 https://packages.adoptium.net/artifactory/deb bookworm InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 843C48A565F8F04B Reading package lists... W: GPG error: https://packages.adoptium.net/artifactory/deb bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 843C48A565F8F04B E: The repository 'https://packages.adoptium.net/artifactory/deb bookworm InRelease' is not signed. ----------------------------------- 📋 View full log (443 lines): /root/.install-1d23d771.log ✖️ Installation failed in container 115 (exit code: 100) ✔ Installation log: /tmp/install-lxc-115-1d23d771.log Remove broken container 115? (Y/n) [auto-remove in 60s]: n Container 115 kept for debugging root@pvemain:~# ### 🖼️ Additional context (optional). Script: Omada Controller (ct/omada.sh) Proxmox: 9.1.4, Debian 12, unprivileged LXC Exact failure: apt update fails on Adoptium repo key Error: NO_PUBKEY 843C48A565F8F04B, repository not signed Root cause: script adds Adoptium repo and runs apt update before importing the repo key, and it uses a deb822 .sources file (adoptium.sources) so wildcard delete of *.list does not remove it Fix request: import Adoptium key and write it to /etc/apt/keyrings before adding the repo and before any apt update, also handle .sources files Optional improvement: force APT to IPv4 if container has no IPv6, or document it

kerem

2026-02-26 12:52:38 +03:00

closed this issue
added the
bug
label

kerem referenced this issue

2026-02-26 13:34:39 +03:00

[PR #2494] [MERGED] Fix: Actual Budget, add missing .env when updating #3790

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2494

No description provided.

Rows
Columns