kraft cloud compose doesn't list instances after they have been created

[tatodorov]

Describe the bug

I've tried the compose example from here:
https://github.com/kraftcloud/examples/tree/main/tyk

After I execute kraft cloud compose up -d, it creates the instances, but it returns an output stating that they are in stopped state.
However, when I list the instances with kraft cloud instances ls, I can see they are in running state.
When I execute kraft cloud compose ps, it states that neither of the services is being deployed.
The instances and service groups can't be managed with kraft cloud compose.
The only way to stop/delete them is with the kraft cloud inst rm --all and kraft cloud svc rm --all.

Steps to reproduce

1. Checkout this repository:
   https://github.com/kraftcloud/examples.git
2. cd to tyk

$ kraft cloud compose up -d
 W  could not parse image name: invalid reference format: repository name must be lowercase
[+] building rootfs... done!                                                                                                                                                                                                                                       x86_64 [2.3s]
[+] packaging index.unikraft.io/todorov/tyk... done!                                                                                                                                                                                                    kraftcloud/x86_64 [0.0s]
[+] pushing index.unikraft.io/todorov/tyk:latest (kraftcloud/x86_64)... done!                                                                                                                                                                                             [2.0s]
 i  creating service group network=tyk-default
 i  deploying image=index.unikraft.io/todorov/tyk:latest
 i  deploying image=redis:latest
 i  starting 2 instance(s)
NAME       FQDN                                  STATE    STATUS  IMAGE                                                                      MEMORY   ARGS                                         BOOT TIME
tyk-tyk    tyk-default-ng5f8o7e.fra0.kraft.host  stopped          todorov/tyk@sha256:a274a71acad1d8d84901bbfbc4dba1162cb33df507969729da9...  128 MiB  /usr/bin/tyk start --conf /etc/tyk.conf      0.00 ms
tyk-redis  tyk-default-ng5f8o7e.fra0.kraft.host  stopped          redis@sha256:6304602326da3a7ec82cfff1c8640bf4abf2fb3b25b8c7e0a7eeebf0a...  512 MiB  /usr/bin/redis-server /etc/redis/redis.conf  0.00 ms

$ kraft cloud compose ps
NAME   FQDN  STATE  STATUS        IMAGE  MEMORY  ARGS  BOOT TIME
tyk                 not deployed
redis               not deployed

$ kraft cloud instances ls
NAME       FQDN                                  STATE    STATUS        IMAGE                                                                    MEMORY   ARGS                                         BOOT TIME
tyk-redis  tyk-default-ng5f8o7e.fra0.kraft.host  running  since 20secs  redis@sha256:6304602326da3a7ec82cfff1c8640bf4abf2fb3b25b8c7e0a7eeebf...  512 MiB  /usr/bin/redis-server /etc/redis/redis.conf  27.50 ms
tyk-tyk    tyk-default-ng5f8o7e.fra0.kraft.host  running  since 20secs  todorov/tyk@sha256:a274a71acad1d8d84901bbfbc4dba1162cb33df507969729d...  128 MiB  /usr/bin/tyk start --conf /etc/tyk.conf      51.70 ms

$ kraft cloud compose ps
NAME   FQDN  STATE  STATUS        IMAGE  MEMORY  ARGS  BOOT TIME
tyk                 not deployed
redis               not deployed

Expected behavior

kraft cloud compose up -d should not return that the instances are in stopped state if they are actually running.
kraft cloud compose ps should not return not deployed if the instances are in fact deployed and running.
kraft cloud compose down should stop and remove the instances.

Which architectures were you using or does this bug affect?

No response

Which operating system were you using or does this bug affect?

No response

Relevant log output

No response

[craciunoiuc]

@tatodorov does this still happen?

I tried it out with latest staging and only the stopped instances bug showed up, but the rest worked

[tatodorov]

@craciunoiuc , indeed now the only issue I can see is that after executing kraft cloud compose up -d, I see it states that the instances are in status stopped, although they are actually running.
When I execute kraft cloud compose ps afterwards, I can see the correct status of the instances.