The "no new privileges" flag is set, which prevents sudo from running as root.

[bluecough]

Just installed a new RPi5 running on Trixie. Went to install Allsky and getting sudo issues when trying to update the config.

"Failed to update settings in '/home/allsky/allsky/config/settings.json': Unable to update '/home/allsky/allsky/config/settings.json': sudo: The "no new privileges" flag is set, which prevents sudo from running as root.
sudo: If sudo is running in a container, you may need to adjust the container configuration to disable the flag."

I am not running on a container. Also the install.sh script should be updated to reflect the new OS rather than bookworm.

[EricClaeys]

@bluecough, Trixie came out just a few days ago and we only knew about it when another user said Allsky didn't install on it.
We need to test Allsky on it, and have no idea if that's a 1-day effort or 1-month. In the meantime, please use Bookworm.
If you can figure out how to get Allsky to install and work, let us know - that will greatly reduce the time we need fully testing it.

FYI, I posted on the Allsky Facebook group telling users not to use Trixie with Allsky until we've tested it.

@Alex-developer, FYI on the "no new privileges" flag, which I assume is new in Trixie?

[gstrauss]

Please see BEHAVIOR CHANGES in https://wiki.lighttpd.net/Release-1_4_79 for instructions how to override lighttpd default systemd hardening settings:

To create overrides, systemctl edit lighttpd and edit /etc/systemd/system/lighttpd.service.d/override.conf

[Alex-developer]

@gstrauss

Thanks for that, we have all the details to support Trixie, there are a few other changes that are needed.

I have allsky running on trixie

I will try and look at this over the next week or so.

[EricClaeys]

@bluecough,
I assume you got the "no new privileges" message when in the WebUI, probably trying to update a setting?
If so, please go to that page and press F12, then in the stuff that appears on the right, go to the "Console" tab.
Then try updating a setting. If there's anything in the Console, please take a screenshot of the browser windows showing the URL, the error message, and the Console.
Thanks - Eric

[bluecough]

Thanks for responding so quickly. I only decided on Friday to rebuild an all sky camera so I wasn't aware of the issues nor the latest OS update. (I have been using your software for years but took it down two years ago and finally came back).

See attached for the requested. I also performed a chmod 777 on the config directory to see. I also checked /etc/sudoers and there isn't a flag regarding "no new privileges"

[EricClaeys]

@bluecough,
Welcome back to Allsky!!

on the pink line, please click on the "index.php..." link on the right then take a screenshot of what pops up.

The "read only filesystem" error message is misleading, but just to make sure, run:

cd ~/allsky/config
touch x && rm x

that will try and create a file then remove it. If you get an error, there"s something else going on.

[bluecough]

No issues on creating and removing a file from config directory.

I tried the bookworm OS version and installed fine with no issues following the install precisely. So I went back to Trixie and in order to run install.sh successfully I and to create a python venv first before running install.sh otherwise I get the following:

`***************************************
*** Welcome to the Allsky Installer ***

---

• Installing initial dependencies.
• Found RPi HQ (imx477)
• Using user-selected RPi HQ camera.

*** NOTICE:

---

The following steps can take up to an hour depending on the speed of
your Pi and how many of the necessary dependencies are already installed.

---

• Installing the web server.
• Creating new /var/log/lighttpd/error.log.
• Installing dependencies.
• Creating Allsky commands.
• Modifying variables for WebUI and Website.
• Setting up WebUI options and default settings for RPi cameras.
• Installing PHP modules and dependencies.

*** WARNING:

---

Unknown operating system: trixie.

---

• Installing Python_dependencies:
• === Package # 1 of 15: [numpy]

*** ERROR:

---

Python_dependencies [numpy] failed

---

• The full log file is in /home/redacted/allsky/config/logs/Python_dependencies.1.log
  The end of the file is:

    If you wish to install a non-Debian-packaged Python package,
    create a virtual environment using python3 -m venv path/to/venv.
    Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
    sure you have python3-full installed.
  
    For more information visit http://rptl.io/venv
  

  note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
  hint: See PEP 668 for the detailed specification.`

[EricClaeys]

Failing when installing numpy is the same problem the other trixie user had. We'll look into it but it may be a few weeks. Please use Bookworm in the meantime.

[cafuego]

I got rid of the "no new privileges" message by editing /etc/systemd/system/multi-user.target.wants/lighttpd.service and changing NoNewPrivileges=yes to NoNewPrivileges=false in the [Service] section. However, I'm getting the "Read-only file system" warning now.

And a bit of digging shows that the ProtectHome=read-only line in lighttpd.service is the culprit there. Commenting that out out changing it to ProtectHome=no and then re-loading the unit file and restarting lighttpd.

One more set of changes needed for Trixie is the sudoers.d snippet. There are no binaries in /bin and /sbin anymore, both of those are symlinks and everything is in /usr/(s)?bin instead.

[Alex-developer]

I got rid of the "no new privileges" message by editing /etc/systemd/system/multi-user.target.wants/lighttpd.service and changing NoNewPrivileges=yes to NoNewPrivileges=false in the [Service] section. However, I'm getting the "Read-only file system" warning now.

And a bit of digging shows that the ProtectHome=read-only line in lighttpd.service is the culprit there. Commenting that out out changing it to ProtectHome=no and then re-loading the unit file and restarting lighttpd.

One more set of changes needed for Trixie is the sudoers.d snippet. There are no binaries in /bin and /sbin anymore, both of those are symlinks and everything is in /usr/(s)?bin instead.

There is a simpler solution, switch to php-fpm, plus a few changes in the installer.

The v2025.xx.xx branch has all of these changes in it