Docker Desktop error tpotinit is unhealthy (T-Pot 24.04)

[IKMAR00]

Hello.

I am new to honeypots and my intention is to build a new honeypot for learning purposes.

I am trying to deploy the base project in a test environment (Windows 10 Home machine with Docker Desktop as the guide indicates).

Executing genuser.sh works perfectly but, when executing docker compose up, I keep getting this error caused by tpotinit:

In Docker Desktop I also have enabled WSL integration and Ubuntu.

Is there any step that I missed, or this is another type of issue?
Thank you in advance!

[t3chn0m4g3]

Based on the info provided it looks like you have not copied the proper compose file and / or set T-Pot to run on Win in .env.

[IKMAR00]

Executing the updated .\genuser.sh causes the same effects has before, the pop-up window from Git for Windows with the same message.

However, executing bash genuser.sh doesn’t show the previous error; it creates the container, but doesn't update the .env file. Removing -u 1000:1000 doesn’t make a difference in this step.

I tried to manually input the user with the brackets it showed in the output console, but it showed the same error: tpotinit is unhealthy, and the output was three times instead of one.

I have also tried to put the user without the brackets [] but it still showed that tpotinit is unhealthy.

[t3chn0m4g3]

Thanks. I could finally reproduce this with a complete fresh Win 11 / Docker Desktop install. It seems Docker Desktop switched to WSL2 internally which shows up the Docker VM uname -a actually as linux instead of linuxkit which in turn leaves entrypoint.sh with improper checks.
Switching back to WSL will not help, because docker compose handles volumes differently on Windows, now all volume file handles must be present at the project start, instead of the individual container which results in nginxpasswd always missing.
I have a working prototype now, but this still needs refinement and testing with Linux, macOS versions before being pushed.

[IKMAR00]

Oh, good!

I'll be waiting for the new version when it's ready.

Thank you so much for everything!

[t3chn0m4g3]

I just pushed the changes.
At best you run a git reset --hard and then a git pull and follow the ReadMe.

[IKMAR00]

Yes!
It's working!

I also noticed that Ciscoasa gets triggered if you execute docker compose up after stopping T-Pot with CTRL-C.
It has to be a false positive since, by default, Windows firewall blocks access from remote as the ReadMe indicates.

No other honeypots get triggered except Ciscoasa, and, if I am not mistaken, setting up T-Pot in an unfiltered zone should register attacks from multiple honeypots in a few minutes.

Thank you for everything!