Pull Policy Error

[kanowah]

When I'm trying to install the new version, I'm getting the following error, I've tried to installed it on different devices still same:

[t3chn0m4g3]

Check the docker-compose.yml, it looks like you made changes around the map_web service and now T-Pot cannot start due to a missing setting.

[kanowah]

It's a fresh installation, I have not change any file at all

…

On Tue, Jul 23, 2024 at 2:52 PM Marco Ochse ***@***.***> wrote: Check the docker-compose.yml, it looks like you made changes around the map_web service and now T-Pot cannot start due to a missing setting. — Reply to this email directly, view it on GitHub <#1623 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARLFCCEKZYYRXCTIKH2MMMLZNYYWJAVCNFSM6AAAAABLKEVN4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBUHA4DQMRXGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[kanowah]

I've only used the following command:

env bash -c "$(curl -sL https://github.com/telekom-security/tpotce/raw/master/install.sh)"

[t3chn0m4g3]

Then post the docker-compose.yml as formatted markdown because I cannot reproduce it and provide infos about your OS and such.

[akajhon]

Same problem here @kanowah and @t3chn0m4g3 !

When fresh installing via env bash -c "$(curl -sL https://github.com/telekom-security/tpotce/raw/master/install.sh)" using the default docker-compose.yml without changes, the message about the pull_policy is frequent.

Even when executing sudo systemctl start tpot the message for the pull_policy is raised and the docker containers do not start as usual.

I`ve been using an Ubuntu 22.04 live server.

[kanowah]

I'm using the old TPot iso file from https://github.com/telekom-security/tpotce/releases/download/22.04.0/tpot_amd64.iso as it is light, the code is too long, here is a snippet of the docker-compose.yml, it's the default:

## Map Redis Service
  map_redis:
    container_name: map_redis
    restart: always
    depends_on:
      tpotinit:
        condition: service_healthy
    stop_signal: SIGKILL
    tty: true
    image: ${TPOT_REPO}/redis:${TPOT_VERSION}
    pull_policy: ${TPOT_PULL_POLICY}
    read_only: true

## Map Web Service
  map_web:
    container_name: map_web
    restart: always
    depends_on:
      tpotinit:
        condition: service_healthy
    environment:
     - MAP_COMMAND=AttackMapServer.py
    stop_signal: SIGKILL
    tty: true
    ports:
     - "127.0.0.1:64299:64299"
    image: ${TPOT_REPO}/map:${TPOT_VERSION}
    pull_policy: ${TPOT_PULL_POLICY}

## Map Data Service
  map_data:
    container_name: map_data
    restart: always
    depends_on:
      elasticsearch:
        condition: service_healthy
    environment:
     - MAP_COMMAND=DataServer_v2.py
     - TPOT_ATTACKMAP_TEXT=${TPOT_ATTACKMAP_TEXT}
     - TZ=${TPOT_ATTACKMAP_TEXT_TIMEZONE}
    stop_signal: SIGKILL
    tty: true
    image: ${TPOT_REPO}/map:${TPOT_VERSION}
    pull_policy: ${TPOT_PULL_POLICY}

[t3chn0m4g3]

Thanks for the update, I can now reproduce it with a completely fresh install on Debian 12.
It looks like a new docker version is the culprit.

[mygitcrazy]

I also spinned up a fresh installation a couple of days ago and it worked instantly. Today i installed the same installation again, and also getting the error as posted in this thread....

Ubuntu 24.04 and tried Debian 12 (same problem)

[t3chn0m4g3]

A possible workaround...

Run sudo apt-cache madison docker-compose-plugin and it will spit out all the available repo versions:

docker-compose-plugin | 2.29.0-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable arm64 Packages
docker-compose-plugin | 2.28.1-1~debian.12~bookworm | https://download.docker.com/linux/debian bookworm/stable arm64 Packages
[...]

We are only interested in the 2.28 branch and you can now install it with...
sudo apt-get install docker-compose-plugin=2.28.1-1~debian.12~bookworm

Then goto $HOME/tpotce and run docker compose pull and then sudo reboot.

Let me know if this works and I will update this for other OS installs if requested.

[mygitcrazy]

Up and running 🎉
This (workaround) did work for me!!

Big thanks @t3chn0m4g3

[t3chn0m4g3]

Thanks for the quick feedback @mygitcrazy! Happy it is working 🤩

[akajhon]

Works like a charm! Thanks for the fast help @t3chn0m4g3 !

[t3chn0m4g3]

@akajhon Appreciate the fast response! Happy it is working for you, too! 🤩

[t3chn0m4g3]

I will monitor this and as soon as Docker releases a fixed version I will update this issue accordingly.

Thanks @mygitcrazy @akajhon @kanowah for bringing this up and testing the workaround.

[t3chn0m4g3]

The upstream issue has been closed and the fix is available in the 2.29.1 release. No details in the description, though and package not yet pushed to Docker Linux repositories.

[t3chn0m4g3]

The new docker-compose-plugin was pushed to the Docker Linux repositories, just tested it and I can confirm this is resolved now.