W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument

[diakbar]

I got that error when trying apt-get install in KALI Linux deploy using Android Apps Linux Deploy.
Is there something I missing from installation??

[nbraunstein]

I have gotten this same error all day. Two fresh installs on a pi

[lacroutelacroute]

me too fresh install today

[charzhar]

Need help with this too

[jedau]

I have encountered this as well on a fresh Kali armhf on a pi3. The previous time I didn't encounter this. Would be great if there's a resolution to this.

[willinspire]

Running Pi-3 with Kali for months now with no issues. Started encountering this issue today during an attempt to apt-get update

[cseedz]

Same problem here...

[jamall007]

Same here, I'm on a Rasp Pi 3 model B. I encountered the error when I attempted to run
apt-get install linux-headers-$(uname -r)

[nbraunstein]

Rpi3 here too

…

On Sun, Nov 12, 2017 at 3:52 PM, jamall007 ***@***.***> wrote: Same here, I'm on a Rasp Pi 3 model B. I encountered the error when I attempted to run apt-get install linux-headers-$(uname -r) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#869 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYHiFnmxhS-oIPVd3OTVZQWKIK8UMV1Jks5s14SwgaJpZM4QR94a> .

-- Noah Braunstein [email protected]

[jamall007]

One of the following packages is the culprit, everything was fine before I did this upgrade:

Start-Date: 2017-11-11 13:48:06
Commandline: apt-get upgrade -y
Upgrade: libapt-inst2.0:armhf (1.6alpha3, 1.6alpha4), libegl1:armhf (0.2.999+git20170802-5, 1.0.0-1), libexpat1-dev:armhf (2.2.3-1, 2.2.3-2), apt:armhf (1.6alpha3, 1.6alpha4), libgl1:armhf (0.2.999+git20170802-5, 1.0.0-1), libbsd0:armhf (0.8.6-2, 0.8.6-3), libgles2:armhf (0.2.999+git20170802-5, 1.0.0-1), libapt-pkg5.0:armhf (1.6alpha3, 1.6alpha4), libexpat1:armhf (2.2.3-1, 2.2.3-2), libapparmor1:armhf (2.11.1-2, 2.11.1-3), libglx0:armhf (0.2.999+git20170802-5, 1.0.0-1), libdbus-glib-1-2:armhf (0.108-2, 0.108-3), apt-utils:armhf (1.6alpha3, 1.6alpha4), libxres1:armhf (2:1.0.7-3, 2:1.2.0-2), libglvnd0:armhf (0.2.999+git20170802-5, 1.0.0-1)
End-Date: 2017-11-11 13:49:06

[sk3lk0]

how fix?

[Jinovas]

getting this error too on my nexus 7, but not my nexus 5 though...hmm

[sgt-pepper920]

Day 2 same error thinking it's an issue with arm version my computer apt-get update fine but rpi3 I am receiving the same err there as everyone else

[Dunuin]

I have the same problem. I tried to install "raspi3-firmware" but it failed because of a not mounted "/boot". I changed the "/etc/fstab" for "/boot" from "noauto" to "auto", rebooted and since then "apt-get update" returns this error.
I used PINN to install Kali to my Raspi3.

[sgt-pepper920]

it seemed to try a little harder this morning but still receiving the same error
Get:1 http://archive-7.kali.org/kali kali-rolling InRelease [30.5 kB] Get:2 http://archive-7.kali.org/kali kali-rolling/main Sources [11.6 MB] Get:3 http://archive-7.kali.org/kali kali-rolling/contrib Sources [66.6 kB] Get:4 http://archive-7.kali.org/kali kali-rolling/main armhf Packages [15.1 MB] Get:5 http://archive-7.kali.org/kali kali-rolling/contrib armhf Packages [94.9 kB] Fetched 26.9 MB in 29s (914 kB/s) Reading package lists... Done W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument W: store: aptMethod::Configuration: could not load seccomp policy: Invalid argument

[nbraunstein]

Does anyone else have slim installed? Is this issue happening after "apt-get dist-upgrade" Have you tried "sudo apt get update -y" "dkpg --reconfigure -a" I have also performed a fresh install, I installed one package at a time and reboot it after each one. Anyone else try ethernet instead wifi? I have fixed my issue with a fresh install, although I'm not sure what I did.

…

On Nov 16, 2017 07:56, "sgt-pepper920" ***@***.***> wrote: it seemed to try a little harder this morning but still receiving the same error Get:1 http://archive-7.kali.org/kali kali-rolling InRelease [30.5 kB] Get:2 http://archive-7.kali.org/kali kali-rolling/main Sources [11.6 MB] Get:3 http://archive-7.kali.org/kali kali-rolling/contrib Sources [66.6 kB] Get:4 http://archive-7.kali.org/kali kali-rolling/main armhf Packages [15.1 MB] Get:5 http://archive-7.kali.org/kali kali-rolling/contrib armhf Packages [94.9 kB] Fetched 26.9 MB in 29s (914 kB/s) Reading package lists... Done W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument W: store: aptMethod::Configuration: could not load seccomp policy: Invalid argument — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#869 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYHiFqrhUWjhfJNv9AumT_LQszv7iyiFks5s3FtHgaJpZM4QR94a> .

[Dunuin]

it seemed to try a little harder this morning but still receiving the same error

Same here.

Does anyone else have slim installed? Is this issue happening after
"apt-get dist-upgrade"

I never did an dist-upgrade. Only "apt-get update && apt-get upgrade" once every 1 to 3 days.

Have you tried "sudo apt get update -y"

Its the same problem with "apt-get update -y".

"dkpg --reconfigure -a"

"dpkg-reconfigure -a" isn't working. It needs a package specified.

Anyone else try ethernet instead wifi?

Only Wifi.

Edit:
I did an "apt-get dist-upgrade" now and it updated and installed many packages but encountered several errors while processing:
udev, udisk2, xserver-xorg-core, xserver-xorg-input-wacom, xserver-xorg-input-synaptics, gvfs-daemons, xserver-xorg-input-evdev, xserver-xorg-video-fbdev, xserver-xorg-input-libinput, gvfs:armhf, x-server-xorg-input-all

[julian-klode]

It means your kernel does not support seccomp, or you are using an emulation layer that does not support seccomp.

It is not an error. It is a warning I added temporarily to see if turning that off for people who do not have seccomp works correctly. It will go away in a later apt release.

[jedau]

@julian-klode Thanks for the clarification, man!

[sgt-pepper920]

Was there a fix to this as of yet it's months later and I'm still getting this

[gjertmagnus]

Suddenly that "error" appers . Would really appriciate some help on this issue. Thanks

[darkt1981]

So any eta on when this will be fixed ? its been over a month now ?

[reybango]

@julian-klode when do you plan on remove this? It's a blocking issue now.

[Rakitic]

I can't get round this problem.I just installed Kali Linux and i am using android vnc viewer but I can't remove the error w: http: aptMethod:: configuration: could not load seccomp policy: Invalid argument

[adrian-rt]

same I have this issues on WSL .

[NatoBoram]

Fresh WSL install on fresh W10 install, got this error! Also cat /etc/resolv.conf returns nameserver 8.8.8.8.
Error :

W: http: aptMethod::Configuration: could not load seccomp policy: Invalid argument

[Xudmud]

To be fair... W: is Warning, not necessarily an error. I too had this warning come up, which I'm assuming is something WSL-related. Doesn't seem to be impacting functionality, however.

Also cat /etc/resolv.conf returns nameserver 8.8.8.8.

8.8.8.8 is Google's public DNS nameserver, so if you're using that in Windows it'll use the same in whatever WSL distro you're using.
(https://en.wikipedia.org/wiki/Google_Public_DNS)

[Z3r0Un1x]

Same error

[qu4nd]

Same for subsystem on Windows. Just in case that's of any interest.

[maoxian-1]

Same for subsystem on Windows.

[galenguyer]

Same for fresh install of Kali Rolling on Subsystem for Windows on Build 16299.248.
Error shows up anytime I use apt update or apt upgrade.
Kali version info:

PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2018.1"
VERSION_ID="2018.1"
ID_LIKE=debian

[darkt1981]

no such file or directory ?

[R3dB0b]

Best to run as root first, type the following
sudo su - root

You will be prompted to enter your password. The above command sudo allows you to run as different user, Su is super user access then - root is the command to run as

Once the cursor shows the user as root instead of the user you created then run the command
echo 'apt::sandbox::seccomp "false";' > /etc/apt/apt.conf.d/999seccomp

[R3dB0b]

Typo sorry no work word at the end

[darkt1981]

for me after runnign that command its show me this:

">"

and is waiting for a input, seems like its not echoing the command

[R3dB0b]

It's all one line no carriage return. The comment box separates it in two lines on github

[darkt1981]

thanks i alreayd made the file manuel its fixed now thank god xD

[BosnaZmaj]

Thanks @R3dB0b, that did the trick

[qu4nd]

Working with @R3dB0b 's solution here as well!

[MetaFight]

TO REITERATE: This is not an error. There is nothing to fix.

See #869 (comment)

Sudo'ing commands you don't understand from the internet is not a solution.

[R3dB0b]

The sandboxing mechanism doesn't allow to run certain commands on WSL such as when attempting to do apt-get. Please be careful and ideally only use the commands above to resolve the error you get in Windows Store sources Kali Linux and the issue seccomp works in that hybrid virtualized environment. Redeploy Kali once the issue is fixed.

[StoneOnFluff]

Hey @R3dB0b I've run into an isue with
"Best to run as root first, type the following
sudo su - root

You will be prompted to enter your password. The above command sudo allows you to run as different user, Su is super user access then - root is the command to run as

Once the cursor shows the user as root instead of the user you created then run the command
echo 'apt::sandbox::seccomp "false";' > /etc/apt/apt.conf.d/999seccomp"

I recieved the issue -su: /ect/apt/apt.conf.d/999seccomp: No such file or directory.

and i am running The kali linux from the windows 10 store.

Please help. Thanks.

[darkt1981]

to fix this try this, it worked for me seeing the above command is correct but github doesnt like the ">" icoon.

1. goto console

2. type : su root

3. input your root password.

4. sudo nano /etc/apt/apt.conf.d (this should open editor nano with the file or create it if its not there)

5. in the editor type :

apt::sandbox::seccomp "false";

press CTRL + X , save the file.

[darkt1981]

6. now back in console type : sudo apt-update.

should work now, if not reboot and try step 6 again.

7. if it keeps saying it cant find the repository, check to see if your sources.list has the latest one correctly set.

[darkt1981]

sorry i made a typo at step 6:

its : sudo apt-get update

[R3dB0b]

Darkt1981 stuff will work

Also make sure the command is run as one line. It's not split in two. Let us know if it still doesn't work

[KBClayton]

darkt1981 worked for me with the one tweak that /etc/apt/apt.conf.d is a directory but just putting it in /etc/apt/apt.conf worked.

[darkt1981]

i see make another error.

step 4.
sudo nano /etc/apt/apt.conf.d/999seccomp (this should open editor nano with the file or create it if its not there)

[darkt1981]

Cleaned up Fix:

somehow writing the fix told by the other gut didnt work for me so here the longer way to the same result.

to fix this try this, it worked for me seeing the above command is correct but github doesnt like the ">" icoon.

goto console

type : su root

input your root password.

sudo nano /etc/apt/apt.conf.d/999seccomp (this should open editor nano with the file or create it if its not there)

in the editor type :

apt::sandbox::seccomp "false";

press CTRL + X , save the file.

6. now back in console type : sudo apt-get update.
   this should work now, if not reboot and try step 6 again.

if it keeps saying it cant find the repository, check to see if your sources.list has the latest one correctly set.

[Ma5onic]

Thanks @darkt1981!
I would like to add that this also solves the same error that may appear when installing kali from the windows store.

The only difference is that you need to start at:
sudo nano /etc/apt/apt.conf.d/999seccomp

[Surrogard]

People relax, it is a warning, you can safely ignore it. Apt-get and any other programs should still do their work just fine.
@windows10 users that just want to try Linux: don't prevent the warning by adding the seccomp file in apt.conf.d, the Windows Subsystem for Linux is in a state of flux and you might generate later problems by doing that.

[iceman-twitch]

i updated source.list
added apt::sandbox::seccomp "false"; sudo nano /etc/apt/apt.conf.d/999seccomp
really annoying now wat to do on linux subsystem version.

Err:1 http://http.kali.org/kali kali-rolling/main amd64 perl-modules-5.26 all 5.26.1-5
  Temporary failure resolving 'http.kali.org'

it is doing many attempts on different stuffs.

[julian-klode]

I disabled the seccomp sandbox in apt 1.6~rc1, so it's been "fixed" for a while now in bionic. It'll probably turn back on again next cycle, though, with some more tweaks.

[R3dB0b]

Cool thanks having seccomp on WSL working without having to disable it would be sweet. At least learning to troubleshoot the issue has helped me learn more about sandboxing in Linux. :)

[R3dB0b]

Kem008 check DNS resolution is working on the machine and that the repo source is still valid it may have changed or the source may have been temporarily down

[jachin99]

@Surrogard i disabled seccomp trying to update. Is seccomp only disabled for the duration of my session? If not is there a quick way to disable it? Is there a way to confirm updates or new packages have been applied by navigating the windows file system? Thanks

[Surrogard]

@jachin99 if you disabled it via the "/etc/apt/apt.conf.d/999seccomp" method then it is permanent as long as the "999seccomp" file exists in that directory.
To your other question: the files from the linux instance lie somewhere on the computer (doesn't seem to be so easy to pinpoint), so you can most likely check if they were updated, but I would advise to do it in the linux shell. The easiest way should be to install something new and try running it afterwards. If it runs, it works ;)
For example you could install the MidnightCommander "mc" if it is not yet installed:
sudo apt-get install mc
should do the trick and after that start mc. You'll know if the software starts or not...
If you want to confirm what packages are installed in what version do a
dpkg -l >before.txt
before the upgrade and a
dpkg -l > after.txt
after it. Then you can use
diff before.txt after.txt
to see the differences

[jachin99]

@Surrogard Thanks for help, and I'll investigate.

[WSLUser]

This occurs in WSL for Debian Buster (Unstable). Don't have a VM to verify if native Debian Buster does this as well. Far as I can tell though seccomp is a soft fail. Packages do install and can be run without issues. It would be nice to have it working though since this wasn't a thing in Debian stable, Ubuntu 16.04 LTS, etc.