[BUG]: Air-gapped instructions; Docker tries to pull images remotely

[InfiniteBSOD]

Version Information

0.14.3

Hashcat

No response

Description

Docker: 27.3.1 build ce12230
WSL2: Ubuntu 24.0.1 (Kernel: 5.15.167.4)
Versions of hashtopolis-frontend and hashtopolis-backend: 0.14.3 (I guess, pulled the docker images 2024-12-08).

Intended result:
Being able to deploy hashtopolis-frontend and hashtopolis-backend on an air-gapped machine.

Actual result:
Docker always tries to fetch the images remotely even though they are downloaded and "loaded" locally.

Reproduction:
On a machine with internet access:
1)

docker pull hashtopolis/backend:latest
docker pull hashtopolis/frontend:latest

and

docker save hashtopolis/backend:latest --output hashtopolis-backend.tar
docker save hashtopolis/frontend:latest --output hashtopolis-frontend.tar

and

wget https://raw.githubusercontent.com/hashtopolis/server/master/docker-compose.yml
wget https://raw.githubusercontent.com/hashtopolis/server/master/env.example -O .env

2. Transfer the files above to the offline computer

On the offline / air-gapped machine:
1)

docker load --input hashtopolis-backend.tar
docker load --input hashtopolis-frontend.tar

"docker images" returns:

REPOSITORY                   TAG
hashtopolis/frontend      latest
hashtopolis/backend      latest

3. "docker compose up" returns:

db Error Get "https://registry-1.docker.io/v2/": dial tcp lookup registry-1.docker.io on <local-ip>... 0.0.s
Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io on <local-ip>:53 no such host.

Inspected "docker-compose.yml" and both images are listed as:

hashtopolis/frontend:latest
hashtopolis/backend:latest

which should conform to what I have locally (see "docker images"):

<image-name>:<tag>
hashtopolis/frontend:latest
hashtopolis/backend:latest

Even tried to rename the images:

docker tag hashtopolis/frontend:latest hashtopolis-frontend:latest
docker tag hashtopolis/backend:latest hashtopolis-backend:latest

if the "/" denotes a remote repository (the repo "hashtopolis" with the images "frontend" and "backend" and both having the "latest" as their tag.

Changed in the docker-compose.yml so it looks for:
hashtopolis-frontend:latest
hashtopolis-backend:latest

Still receive the same error as before.

• Tried checking if I have the variable "DOCKER_HOST" set, which I haven't.
• Added:
  pull_policy: if_not_present
  to the "docker-compose.yml"; no change.
• Tried tagging both images as:

localhost:5000/hashtopolis-backend:latest
localhost:5000/hashtopolis-frontend:latest

and changed the "docker-compose.yml" to reflect the new image names; no change.

Appreciate your help!

Best Regards