Closed gachampiat closed 2 years ago
Running into the same problem with the parrotsec/tools-metasploit image
└──╼ #sh msfconsole-start
postgresql: unrecognized service
msfconsole-start: 3: msfdb: not found
msfconsole-start: 4: msfdb: not found
msfconsole-start: 5: msfd: not found
msfconsole-start: 6: msfconsole: not found
@PalinuroSec
may i ask you why using sh before msfconsole-start? it might alter the $PATH variable. anyways i will trigger an image rebuild as soon as possible to fix the bug
may i ask you why using sh before msfconsole-start? it might alter the $PATH variable. anyways i will trigger an image rebuild as soon as possible to fix the bug
Thank you. Running with bash showed the same:
└──╼ #bash msfconsole-start
postgresql: unrecognized service
msfconsole-start: line 3: msfdb: command not found
msfconsole-start: line 4: msfdb: command not found
msfconsole-start: line 5: msfd: command not found
msfconsole-start: line 6: msfconsole: command not found
ok then the image is totally broken, let me rebuild it
sorry for the long wait, but i take advantage of this weekend to ship the latest version of metasploit too. the new image is being uploaded right now
Hi,
It seems that the docker image stored in docker hub (https://hub.docker.com/r/parrotsec/tools-metasploit) doesn't work. As you can see below I have an error when the container starts
Based on your Makefile, the image metasploit is based on nmap
So I have built the image through the Containerfile available here https://github.com/ParrotSec/docker-images/blob/master/tools/metasploit/Dockerfile
Curiously when I create a container with my local build, the container works correctly.
I have notive that the images don't have the same size
Have you an idea ? Do you know why ?
Thanks