/opt/airgeddon/airgeddon.sh: line 6128: /tmp/nws-01.csv: No such file or directory about airgeddon HOT 2 CLOSED

Please, stop creating issues copying and pasting everything as is because the asterisks are interpreted by markdown as bold. Use screenshots instead next time.

I see in your data you are launching docker from a standard non-root account. Try to launch docker run with sudo or as root.

Anyway I think is not related to docker. What about launching it in native mode without using docker? Are you able to capture packets?

from airgeddon.

Ok the problem here is that your xterm windows can't reach your host X Window system. By default, on docker the DISPLAY used is ":0". So be pretty sure of having your X running there.

1. Be sure of having an X windows system running on your host.
2. Check where are they listening. You can check it launching env | grep DISPLAY

As I said, usually they are on ":0" and if that is the case it should work. If you have in ":1" for example, you must modify your docker run command to set the DISPLAY var pointing to the right place. So you should add -e DISPLAY=:1 to your docker run command.

I updated right now Linux Docker Wiki Section with a new parameter which does this automatically. So your command should be:

docker run --rm -ti --name airgeddon --net=host --privileged -p 3000:3000 -v /home/localhost/AirgeDDon:/io -e DISPLAY=$(env | grep DISPLAY | awk -F "=" '{print $2}') v1s1t0r1sh3r3/airgeddon

The key to see if it worked is the xdpy resolution detection. If the resolution is not detected something went wrong and probably the xterms are going to fail.

Closing.

from airgeddon.