-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: (Proxmox/Debian) kickstart not working, couldn't be accessed by user '_apt'
#16975
Comments
This step
of kickstart failed silently. So you ended up with a netdata package from Debian repos. Let's see if this was a transient error for you or it's a consistent error.
At any case you bumped into a bug, we need to catch this case and fall back or exit |
Here's what I did:
I thought the transient error was strange:
Again I encounter this issue: Edit: I also have a second Proxmox host which has a similar configuration, and it has the exact same error. Any advice? |
couldn't be accessed by user '_apt'
Sorry for the delay, I asked @Ferroin to check your ticket. In the meantime some WAs that might help you
|
@tkatsoulas static build install worked. Alternate temp dir erred with the same issue (except in a different directory). Of note, I ran into this issue where it tried to create an |
just a note: static build has no systemd-journal plugin. |
This issue has been fixed. Installing Netdata on Proxmox 8.2.4 (debian12) works without issues. |
Bug description
I signed up for the cloud trial and tried the
wget
instructions on my Proxmox (debian) system, but it failed, saying that it was built with--disable-cloud
optionExpected behavior
The kickstart should work
Steps to reproduce
...
Installation method
kickstart.sh
System info
Netdata build info
Additional info
Install logs:
The first sign of trouble is:
N: Download is performed unsandboxed as root as file '/tmp/netdata-kickstart-X70OXCYHSn/netdata-repo_2-2+debian12_all.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
The text was updated successfully, but these errors were encountered: