Failed to open the log file: open /.config/amass/amass.log: permission denied

[spekulatius]

Hey @caffix,

when running amass via the docker image I get an permission issue: Failed to open the log file: open /.config/amass/amass.log: permission denied. I've found #732 and confirmed it's in master as expected and my docker image should be up-to-date.

I've installed it recently using:

$ docker pull caffix/amass:latest
latest: Pulling from caffix/amass
63b65145d645: Already exists 
e969121431ac: Pull complete 
ef483f74d4b3: Pull complete 
b74a21ea42bd: Pull complete 
Digest: sha256:31ae1abc8ec9998e5b7d5a65eae9b0f409a66a540b3826edee1c94f246f08945
Status: Downloaded newer image for caffix/amass:latest
docker.io/caffix/amass:latest

and tried to run it:

$ docker run -v /tmp/amass/:/.config/amass/ caffix/amass enum -passive -d owasp.org
Failed to open the log file: open /.config/amass/amass.log: permission denied

A bit surprising is the mismatch of the hash compared to the Docker hub:

$ docker images | grep amass
caffix/amass             latest    69e997bc7cd7   4 hours ago     47.3MB

Any ideas what is going wrong? Thanks in advance for your help!

Cheers, Peter

[mzpqnxow]

Hey @caffix,

when running amass via the docker image I get an permission issue: Failed to open the log file: open /.config/amass/amass.log: permission denied. I've found #732 and confirmed it's in master as expected and my docker image should be up-to-date.

I've installed it recently using:

$ docker pull caffix/amass:latest

latest: Pulling from caffix/amass

63b65145d645: Already exists 

e969121431ac: Pull complete 

ef483f74d4b3: Pull complete 

b74a21ea42bd: Pull complete 

Digest: sha256:31ae1abc8ec9998e5b7d5a65eae9b0f409a66a540b3826edee1c94f246f08945

Status: Downloaded newer image for caffix/amass:latest

docker.io/caffix/amass:latest

and tried to run it:

$ docker run -v /tmp/amass/:/.config/amass/ caffix/amass enum -passive -d owasp.org

Failed to open the log file: open /.config/amass/amass.log: permission denied

A bit surprising is the mismatch of the hash compared to the Docker hub:

$ docker images | grep amass

caffix/amass             latest    69e997bc7cd7   4 hours ago     47.3MB

Any ideas what is going wrong? Thanks in advance for your help!

Cheers,

Peter

Maybe try ls -l on that directory/file and see what the owner and file permissions are?

Off the top of my head, the only other time EPERM would be returned would be if you've hit the file descriptor limit of the system, though you can check man -s 2 open and see what other conditions may result in EPERM