Container REPO not set

[alphafox02]

It's been awhile, but I've purchased another GL modem and was going back over my notes. On a new 22.04 setup, same as what I used before in a video, I was able to run the ./container.sh run release-5g. Towards the end of it setting everything up I noticed it mention something about wireless-deep-fuzzer. I don't recall that before.

I exited out of the container, but docker ps shows it still running. I then tried to run ./container.sh run release-5g again.

It then resulted in this, with mention of podman being installed. I thought it was okay running with just docker. I hadn't paid much attention to when/if podman was in-forced, but it seems to maybe be a problem.

dragon@dragon:~/WarDragon$ ./container.sh run release-5g
CONTAINER_REPO not set. Using default: registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer
Podman not found, installing now...
CONTAINER_REPO not set. Using default: registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
ca-certificates is already the newest version (20240203~22.04.1).
curl is already the newest version (7.81.0-1ubuntu1.18).
gnupg is already the newest version (2.2.27-3ubuntu2.1).
0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.
Downloading podman-static version: v4.6.1 ...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 30.2M  100 30.2M    0     0  14.6M      0  0:00:02  0:00:02 --:--:-- 30.4M
Installing podman to /usr/local/
Podman installed!
Error: no such object: "registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer:release-5g-x86_64"
Image not found, pulling now...
CONTAINER_REPO not set. Using default: registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer
Username: ^Cdragon@dragon:~/WarDragon$ ./container.sh run release-5g
CONTAINER_REPO not set. Using default: registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer
Error: no such object: "registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer:release-5g-x86_64"
Image not found, pulling now...
CONTAINER_REPO not set. Using default: registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer
Username: 
Password: 
Error: authenticating creds for "registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer": Requesting bearer token: invalid status code from registry 403 (Forbidden)

[alphafox02]

This seems to have nothing on it and I'm not sure of where it came from?

https://gitlab.com/asset-sutd/

[alphafox02]

This too.. so I'm not sure how the first run of container.sh run release-5g resulted in a running container?
https://www.docker.com/megarbelini/5ghoul

[alphafox02]

Last comment for now, this is what docker ps shows
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
dc7be94affa4 megarbelini/5ghoul:release-5g-x86_64 "/sbin/init" 26 minutes ago Up 26 minutes 5ghoul-release-5g

[alphafox02]

I lied,

This is the top of container.sh - so somehow it was changed after downloading and running container.sh

#!/usr/bin/env bash

set -eo pipefail

if  [[ ! -v CONTAINER_REPO ]]
then
        CONTAINER_REPO=registry.gitlab.com/asset-sutd/software/wireless-deep-fuzzer
        echo "CONTAINER_REPO not set. Using default: $CONTAINER_REPO"
else
        echo "CONTAINER_REPO set to: $CONTAINER_REPO"
fi

CONTAINER_NAME=wdissector
PODMAN_VERSION=v4.6.1
ARCH=$(uname -m)

[alphafox02]

Removing and re-downloading container.sh after having that successful first run to get the docker in place resolve the issue. But something along the lines of running the first time container.sh to get things up and going is modifying the container.sh script itself as I show above.