starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 13 Packages Projects Releases 10 Wiki Activity

SQL Server 2022 LXC - gpg error #499

New Issue
Closed
opened 2026-02-04 19:20:14 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 19:20:14 +03:00
Owner
Copy Link

Originally created by @Waturus on GitHub (Feb 14, 2025).

✅ Have you read and understood the above guidelines?

yes

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

SQL Server 2022 LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/sqlserver2022.sh)"

📝 Provide a clear and concise description of the issue.

While installing, after installing dependencies I get an error:

✔️ Installed Dependencies
Hit:1 http://archive.ubuntu.com/ubuntu jammy InReleaseoft.com/ubuntu/22.04/mssql-server-2022 jammy main
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Get:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease [3,624 B]
Err:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF
Reading package lists... Done
W: GPG error: https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF
E: The repository 'https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
⠸
[ERROR] in line 31: exit code 0: while executing command $STD apt-get update -y

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

No response

🔄 Steps to reproduce the issue.

Start the installation in standard of standard verbose mode.

❌ Paste the full error output (if available).

✔️ Installed Dependencies
Hit:1 http://archive.ubuntu.com/ubuntu jammy InReleaseoft.com/ubuntu/22.04/mssql-server-2022 jammy main
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-security InRelease
Get:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease [3,624 B]
Err:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF
Reading package lists... Done
W: GPG error: https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF
E: The repository 'https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
⠸
[ERROR] in line 31: exit code 0: while executing command $STD apt-get update -y

🖼️ Additional context (optional).

No response

Originally created by @Waturus on GitHub (Feb 14, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? SQL Server 2022 LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/sqlserver2022.sh)" ### 📝 Provide a clear and concise description of the issue. While installing, after installing dependencies I get an error: ✔️ Installed Dependencies Hit:1 http://archive.ubuntu.com/ubuntu jammy InReleaseoft.com/ubuntu/22.04/mssql-server-2022 jammy main Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-security InRelease Get:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease [3,624 B] Err:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF Reading package lists... Done W: GPG error: https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF E: The repository 'https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ⠸ [ERROR] in line 31: exit code 0: while executing command $STD apt-get update -y ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? _No response_ ### 🔄 Steps to reproduce the issue. Start the installation in standard of standard verbose mode. ### ❌ Paste the full error output (if available). ✔️ Installed Dependencies Hit:1 http://archive.ubuntu.com/ubuntu jammy InReleaseoft.com/ubuntu/22.04/mssql-server-2022 jammy main Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-security InRelease Get:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease [3,624 B] Err:4 https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF Reading package lists... Done W: GPG error: https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF E: The repository 'https://packages.microsoft.com/ubuntu/22.04/mssql-server-2022 jammy InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ⠸ [ERROR] in line 31: exit code 0: while executing command $STD apt-get update -y ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 19:20:14 +03:00
OVERLORD commented 2026-02-04 19:20:22 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 14, 2025):

need to be executed as verbose at the moment. its n microsoft thing

@MickLesk commented on GitHub (Feb 14, 2025): need to be executed as verbose at the moment. its n microsoft thing
OVERLORD commented 2026-02-04 19:20:41 +03:00
Author
Owner
Copy Link

@barrettg commented on GitHub (Feb 14, 2025):

I'm receiving the same error (even in verbose mode). From looking through some docs it seems that the keys needs to be installed using the command curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft-prod.gpg. I'd be happy to submit a PR for this - I'm just not sure how to modify the code and test locally.

@barrettg commented on GitHub (Feb 14, 2025): I'm receiving the same error (even in verbose mode). From looking through some [docs](https://learn.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-ver16&tabs=ubuntu2204) it seems that the keys needs to be installed using the command `curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft-prod.gpg`. I'd be happy to submit a PR for this - I'm just not sure how to modify the code and test locally.
OVERLORD commented 2026-02-04 19:20:54 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Feb 14, 2025):

We have resently changed it. it was like this befor and also did not work correctly. You need to try several times. Eventually it will work(last time i checked it took me like 15 tries)

@michelroegl-brunner commented on GitHub (Feb 14, 2025): We have resently changed it. it was like this befor and also did not work correctly. You need to try several times. Eventually it will work(last time i checked it took me like 15 tries)
OVERLORD commented 2026-02-04 19:21:08 +03:00
Author
Owner
Copy Link

@Waturus commented on GitHub (Feb 14, 2025):

I tried it in verbose a few times. It needs the steps barrettg mentioned from the official guide to obtain the key. Put it in at the top and it should work.

@Waturus commented on GitHub (Feb 14, 2025): I tried it in verbose a few times. It needs the steps barrettg mentioned from the official guide to obtain the key. Put it in at the top and it should work.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#499
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?