Docker Build error - Githubissues

asset-group / 5ghoul-5g-nr-attacks

5G NR Attacks against Qualcomm and Mediatek smartphones. Fuzzer included⚡

https://5ghoul.com

GNU General Public License v2.0

504 stars 85 forks source link

Docker Build error #17

Closed Dustin12138 closed 9 months ago

Dustin12138 commented 9 months ago

Hi,

When I built the docker images I noticed the error in the image. The output was generated when I ran the script container.sh.

I created the corresponding directory but when I reran the shell script, I received the same error indicating the container was not running. Also, it seems that no docker container is running:

I'm using Ubuntu 18.04 and the Docker version is the same as suggested. What should I do to solve this problem?

Thanks,

Dustin12138

alphafox02 commented 9 months ago

I’m using 22.04 (DragonOS), are you trying to compile the source or just run the docker? In my case with 22.04 I do not have the issue you’re seeing. Under requirements it mentions that 18.04 had only been tested for bare-metal non docker.

Dustin12138 commented 9 months ago

I’m using 22.04 (DragonOS), are you trying to compile the source or just run the docker? In my case with 22.04 I do not have the issue you’re seeing. Under requirements it mentions that 18.04 had only been tested for bare-metal non docker.

I'm trying to run the docker. It seems that the quick start does not require a specific version of OS.

Matheus-Garbelini commented 9 months ago

Hi,

When I built the docker images I noticed the error in the image. The output was generated when I ran the script container.sh.

I created the corresponding directory but when I reran the shell script, I received the same error indicating the container was not running. Also, it seems that no docker container is running:

I'm using Ubuntu 18.04 and the Docker version is the same as suggested. What should I do to solve this problem?

Thanks,

Dustin12138

Hi, can you remove the &> /dev/null from this line (https://github.com/asset-group/5ghoul-5g-nr-attacks/blob/master/container.sh#L135) and post the output of your terminal here? After creating the .Xauthority file (sudo touch /root/.Xauthority), you might be getting an error from docker when starting the container.

Dustin12138 commented 9 months ago

Hi,

Here is the output after modifying the script.

Matheus-Garbelini commented 9 months ago

Hi @Dustin12138 you can try removing your .Xauth folder. The issue is that docker is expecting a file there, not a folder: sudo rm -rdf /root/.Xauthority. Then you just need to create an empty file with sudo touch /root/.Xauthority.

Dustin12138 commented 9 months ago

Thanks Matheus, the problem is solved. Closing this issue.