Ostinato 1.3.0-1 and Containerlab 0.56.0 - Can't start Ostinato container

[Kevin S]

Hey All,

I have been working in Containerlab, and recently purchased the single user license to deplpoy in Containerlab.

I have my Ostinato's in my topology file:

ost-1:
      group: testers
      kind: linux
      image: ostinato/ostinato:v1.3.0-1
      ports:
        - 5900:5900/tcp
        - 7878:7878/tcp
    ost-2:
      group: testers
      kind: linux
      image: ostinato/ostinato:v1.3.0-1
      ports:
        - 5900:5900/tcp
        - 7878:7878/tcp

I also have the image imported into Docker

REPOSITORY                      TAG        IMAGE ID       CREATED          SIZE
ostinato/ostinato               v1.3.0-1   a3412c4a3bd7   52 minutes ago   773MB

When i go to deploy the lab, everything in the lad deploys successfully, except the Ostinato containers.  Running a debug while trying to deploy I see the following error:

INFO[0002] Creating container: "ost-1"
DEBU[0002] Container "ost-1" create response: {ID: Warnings:[]}
ERRO[0002] failed deploy stage for node "ost-1": Error response from daemon: no command specified
DEBU[0002] Worker 11 terminating...
DEBU[0002] Container "ost-2" create response: {ID: Warnings:[]}
ERRO[0002] failed deploy stage for node "ost-2": Error response from daemon: no command specified
DEBU[0002] Worker 12 terminating...

I searched the forums for the error message - but I didn't get any hits.  Has anyone ran into this before?  Are there any additional debug commands or logs I could look through to sort this out?

Thanks,

Kevin

[Srivats P]

That's strange.

First, please verify the sha1 for the downloaded tgz -

$ sha1sum docker-ostinato-v1.3.0-1.tgz                           954de8ab86067ab760e186d5906efb37cf6f05dc  docker-ostinato-v1.3.0-1.tgz

If the SHA doesn't match, please download the tgz again.

If it matches, are you able to run the image directly using docker?

$ docker run ostinato/ostinato:v1.3.0-1
======================================================================
 VNC: 172.17.0.2:5900 (connect to this IP from VNC client)
======================================================================
Launching VNC Server ...
PORT=5900

The VNC desktop is:      6cf18cc66212:0
^Ccaught signal: 2

If you don't see output like shown above, try explicitly specifying the entry point -

$ docker run --entrypoint ./start-ostinato.sh ostinato/ostinato:v1.3.0-1
======================================================================
 VNC: 172.17.0.2:5900 (connect to this IP from VNC client)
======================================================================
Launching VNC Server ...
PORT=5900

The VNC desktop is:      7819f20e378c:0
^Ccaught signal: 2

If even that doesn't work, try doing a simple ls inside the container

$ docker run --entrypoint /usr/bin/ls ostinato/ostinato:v1.3.0-1
EULA.txt
start-ostinato.sh

Please share the output of all the above commands along with the output of the below command -

docker inspect ostinato/ostinato:v1.3.0-1

Srivats (Founder, Ostinato)
Now generate up to 100Gbps 🚀 with the Ostinato Turbo add-on!

--
Get Ostinato News and Updates on Twitter - Follow @ostinato (http://twitter.com/ostinato)
---
You received this message because you are subscribed to the Google Groups "ostinato" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ostinato+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ostinato/d5c3fd0c-2018-4df6-903d-231bda94f27dn%40googlegroups.com.

[Srivats P]

Can you please delete the image and then reimport from the tgz using docker load -i docker-ostinato-{tag}.tgz

On Fri, 23 Aug, 2024, 21:20 Kevin Shymkiw, <kshy...@gmail.com> wrote:

Srivats,

sha1sum is the same

shasum -a 1 docker-ostinato-v1.3.0-1.tgz
954de8ab86067ab760e186d5906efb37cf6f05dc  docker-ostinato-v1.3.0-1.tgz

I have the image imported into docker already

docker run ostinato/ostinato:v1.3.0-1

docker: Error response from daemon: no command specified.

If i try to docker run the .tgz file

docker run /home/kevins/ostinato/ostinato:v1.3.0-1.tgz
docker: invalid reference format.

With the entrypoint defined

docker run --entrypoint ./start-ostinato.sh ostinato/ostinato:v1.3.0-1

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./start-ostinato.sh": stat ./start-ostinato.sh: no such file or directory: unknown.

Trying to ls inside the container

docker run --entrypoint /usr/bin/ls ostinato/ostinato:v1.3.0-1

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/ls": stat /usr/bin/ls: no such file or directory: unknown.

inspect

docker inspect ostinato/ostinato:v1.3.0-1
[
    {
        "Id": "sha256:a3412c4a3bd7de1cdf8619a1382cad7ad0764db681f5d0bbd20d6c8a32343c91",
        "RepoTags": [
            "ostinato/ostinato:v1.3.0-1"
        ],
        "RepoDigests": [],
        "Parent": "",
        "Comment": "Imported from -",
        "Created": "2024-08-22T18:49:39.300886941Z",
        "DockerVersion": "27.1.2",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": null,
            "Cmd": null,
            "Image": "",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": null
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 772535586,
        "GraphDriver": {
            "Data": {
                "MergedDir": "/var/lib/docker/overlay2/f634872d1ae1381868ea69c4bc88f487be98c0e89db04d297b7c069f783dab7b/merged",
                "UpperDir": "/var/lib/docker/overlay2/f634872d1ae1381868ea69c4bc88f487be98c0e89db04d297b7c069f783dab7b/diff",
                "WorkDir": "/var/lib/docker/overlay2/f634872d1ae1381868ea69c4bc88f487be98c0e89db04d297b7c069f783dab7b/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:52ee682959072c271df5f8591d8679a3f94154a3fa8e152b9807a5903a24b203"
            ]
        },
        "Metadata": {
            "LastTagTime": "2024-08-22T18:49:39.315517853Z"
        }
    }
]

HTH,

Kevin

[Kevin Shymkiw]

Srivats,

sha1sum is the same

shasum -a 1 docker-ostinato-v1.3.0-1.tgz
954de8ab86067ab760e186d5906efb37cf6f05dc  docker-ostinato-v1.3.0-1.tgz

I have the image imported into docker already

docker run ostinato/ostinato:v1.3.0-1

docker: Error response from daemon: no command specified.

If i try to docker run the .tgz file

docker run /home/kevins/ostinato/ostinato:v1.3.0-1.tgz
docker: invalid reference format.

With the entrypoint defined

docker run --entrypoint ./start-ostinato.sh ostinato/ostinato:v1.3.0-1

docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "./start-ostinato.sh": stat ./start-ostinato.sh: no such file or directory: unknown.

Trying to ls inside the container

docker run --entrypoint /usr/bin/ls ostinato/ostinato:v1.3.0-1

[Kevin Shymkiw]

Srivats,

That seems to have resolved the issue

docker image rm -f a3412c4a3bd7
Untagged: ostinato/ostinato:v1.3.0-1
Deleted: sha256:a3412c4a3bd7de1cdf8619a1382cad7ad0764db681f5d0bbd20d6c8a32343c91

docker load -i docker-ostinato-v1.3.0-1.tgz
6515074984c6: Loading layer [==================================================>]  80.32MB/80.32MB
da8fb3864b4f: Loading layer [==================================================>]  692.2MB/692.2MB
Loaded image: ostinato/ostinato:v1.3.0-1

docker run ostinato/ostinato:v1.3.0-1
======================================================================
 VNC: 172.17.0.2:5900 (connect to this IP from VNC client)
======================================================================
Launching VNC Server ...
PORT=5900

The VNC desktop is:      2f8abd599db6:0

Thanks for the help.  I did docker import - so i see i didn't follow the instructions 😆

Kevin

[Srivats P]

Hi Kevin,

Good to hear that "docker image load" worked.

Will see if there's a way that using "docker image import" fails so that others don't fall into this trap!

Srivats (Founder, Ostinato)
Now generate up to 100Gbps 🚀 with the Ostinato Turbo add-on!