SQL Server 2022 error

[marsimgit]

hello, sql server 2022 script has an issue in sqlserver2022-install.sh)

the offending line is

$STD curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor -o /usr/share/keyrings/microsoft-prod.gpg

should be changed in

$STD curl https://packages.microsoft.com/keys/microsoft.asc | sudo tee /etc/apt/trusted.gpg.d/microsoft.asc

I would like to propose the change via pull request but right now I don't know how to, hope someone better skilled would be so kind to integrate the change :-)

bye

[wgshef]

When I was running this script, I received the following error:

 ⠇ Setup SQL Server 2022 
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1
The silent function has suppressed the error, run the script with verbose mode enabled, which will provide more detailed output.

/dev/fd/63: line 116: RANDOM_UUID: unbound variable

So I manually ran each line in the sqlserver2022-install.sh file. This line generated this error as shown:

curl https://packages.microsoft.com/keys/microsoft.asc | sudo tee /etc/apt/trusted.gpg.d/microsoft.asc
-bash: sudo: command not found

It appears that the fix listed above has been implemented.

I manually took out the "sudo" and it ran fine, as did the rest of the script (again, run manually).

It looks like the above fix was copied straight from the Microsoft SQL Install on Linux, and inadvertently included the "sudo" that isn't needed on Proxmox. This needs to be removed.

In the Microsoft install instructions ([]https://learn.microsoft.com/en-us/sql/linux/quickstart-install-connect-ubuntu?view=sql-server-linux-ver16&preserve-view=true&tabs=ubuntu2204), it does use the initial statement mentioned in the first post above, but if that throws a warning about the public key not being available to use the changed one. Is it possible to try the first command, and if that warning is generated then go to the alternate? However, if the alternate always works, then it might be the better way to do this script.

Note that this fixed line is also in the "Installing SQL Server Tools" section - and it properly doesn't have the "sudo" in it. But, does this command need to be run a second time in the script?

[tremor021]

Will be fixed as soon as #2282 merges