Closed l0rddarkf0rce closed 1 week ago
Traceback (most recent call last): File "/usr/bin/docker-compose", line 33, in
sys.exit(load_entry_point('docker-compose==1.29.2', 'console_scripts', 'docker-compose')())
Kali did something recently that broken pretty much everything related to Docker. You're not the first one running into this. The docker-compose
python script (in /usr/bin/docker-compose
) is crashing and throwing an error on Kali because TypeError: kwargs_from_env() got an unexpected keyword argument 'ssl_version'
. There's another open issue from somebody else here that's trying to get Docker and Docker Compose to work on Kali too. They're running into similar issues. I put a solution in there that somebody else said was working for them, so maybe that'll work for you too?
What you're seeing about docker compose in the current directory is that it's simply looking for the standard docker-compose.yml
file, and since it doesn't exist, it creates it and starts adding the Mythic services to it:
2024/08/07 11:57:32 [-] Error while reading in docker-compose file: Config File "docker-compose" Not Found in "[/home/prborg/Mythic]" 2024/08/07 11:57:32 [+] Successfully created new docker-compose.yml file.
Did this work for you?
actually i gave up and ended uninstalling docker-compose all.together and installed the latest docker.io package, which has compose as a command under docker. that fixed all.of my issues. you may want to.close this.
Would you happen to be able to include the steps you took? I can try to update the install file for Kali with Mythic to match what worked for you
when i get back home later this weekend i can send what i did
Get TypeApp for Android
On Aug 14, 2024, 11:45, at 11:45, Cody Thomas @.***> wrote:
Would you happen to be able to include the steps you took? I can try to update the install file for Kali with Mythic to match what worked for you
-- Reply to this email directly or view it on GitHub: https://github.com/its-a-feature/Mythic/issues/397#issuecomment-2289294844 You are receiving this because you authored the thread.
Message ID: @.***>
Steps... Let me see how much I can recreate from memory and zsh history
pulled Mythic to my local computer4. configured .env as needed5. built as per Mythic instructions6. Installed needed modules As you said Kali (or someone) did something to mess up docker-compose. That said the newest versions of Docker already have a compose option so using docker-compose-plugin is not needed. +-------------------------------------------------| Jose J. Cintron| @.***|| "Time is the fire in which we burn..."+-------------------------------------------------
On Wednesday, August 14, 2024 at 12:45:59 PM EDT, Cody Thomas @.***> wrote:
Would you happen to be able to include the steps you took? I can try to update the install file for Kali with Mythic to match what worked for you
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Thank you for these steps! I'll test these out and some other steps people gave on some fresh Kali VMs to see what sticks
Trying to install Mythic on a brand new (fully updated) Kali Linux machine (not a VM). Linux kali 6.8.11-amd64 Docker version: 20.10.25+dfsg1 Docker-compose version: 1.29.2
I pull down mythic with:
git clone https://github.com/its-a-feature/Mythic --depth 1
Build mythic-cli
sudo make
Try to start mythic
sudo -E ./mythic-cli start
I get the following error...
It seems like for some reason mythic-cli is looking for docker compose in the current directory but it is installed where it is supposed to be in
/usr/bin/docker-compose