Docker containers seem to restart endless

[felixKroni]

Hi, Im new to this whole thing but I got the newest tpot version installed on debian 12 and the docker container start when i start the server but it seems like they shutdown after some time. I can get to the Menu at https://:64297 and also open the map even if its empty but i cant access /kibana or /spiderfoot or any other service.

I tried get info about the containers using dps.sh from the docu but i cant find that file. Did it got removes in this version?
I tried to look at the containers using docker ps and docker ps -a

Sometimes there are a lot running:

and sometimes only one is running:

Ive seen in other discussions from last year that ddosspot could be the problem but i dont know how to remove it from the tpot.yml and if that is even a thing anymore.

Thanks for your help

[felixKroni]

Some more information i gathered yesterday:
the tpotinit container restarts every 60sec like defined in the docker-compose. At this point every container gets started but there is no memory overflow as far as i can see it gets to a max usage of 5GB before it all goes down again after about 8sec.

Sometimes i noticed that they were up longer for like 30sec but thats it and all shuts down again.
The commands in htop change though:

In this small period of time before the containers get deleted i looked at some of the docker logs but there is nothing like an error or something
Suricata:

Cowrie:

Elasticsearch:

[felixKroni]

newsflash, it might be a memory problem...
Ive created a custom docker-compose only containing some containers and i get a lot of exit code 137 indicating that the system ran out of memory:

Although i have no clue why there is a "User-initiated shutdown"

[barrydekong]

Hi, I have the same issue even though I reinstalled and update the Tpot again! Anyone can help! thanks.

[felixKroni]

I have solved it for myself by using the ubuntu iso that is provided. That worked pretty straightforward without any Problem. I still have no clue what the problem was using Debian.

[barrydekong]

Thank you!

[FloppyDucks]

I think i know ur issue, glad its working , im pretty sure it is related to the ports that the docker compose file uses when setting up the TPOT, you need to change the default docker compose because a few services use the same ports like 443 and a few others

[barrydekong]

Thank you for your information! I have installed Ubuntu with the same issue and have followed your suggestion to edit the docker-compose.yml file but no clue to change the default setting. Grateful if you can guild how to resolve docker compose file, many thanks.