Add option to list "created" containers which failed to start about crun HOT 8 CLOSED

Nope, just sign your PR, and receive our gratitude. :^)

from crun.

SGTM. @joaompinto Interested in opening a PR?

from crun.

@rhatdan. I will do, please let me know if there are any contribution formal pre-requirements.

from crun.

crun should already list the created containers. I'd need to investigate that. Is it reproducible? Are you running the crun processes from the same context (i.e. same environment variables)?

from crun.

It's reproducible, I am not changing environment, please note that my description for "created" might be inaccurate for this specific test case. There is an error related to the missing --console-socket parameter, but there is a /run/user/1000/crun/container_id/ .

$ crun create random_id
2019-11-08T21:03:35.000929142Z: use --console-socket with create when a terminal is used
~/tmp/test
$ crun create random_id
2019-11-08T21:03:53.000134983Z: container 'random_id' already exists
~/tmp/test
$ crun list
NAME PID       STATUS   BUNDLE PATH                            
~/tmp/test
$ ls -ltrd /run/user/1000/crun/random_id/
drwx------ 2 jpinto jpinto 60 Nov  8 22:03 /run/user/1000/crun/random_id/

from crun.

Anyway, even after creating a container without getting cli errors, I don't get it listed:

$ crun create --console-socket /tmp/test_socket test_id
~/tmp/test
$ crun list
NAME PID       STATUS   BUNDLE PATH                            
~/tmp/test
$ ls -ltr /run/user/1000/crun/test_id/
total 4
prw------- 1 jpinto jpinto    0 Nov  8 22:09 exec.fifo
-rwx------ 1 jpinto jpinto 2555 Nov  8 22:09 config.json
~/tmp/test

from crun.

thanks for the extra info, could you verify if #169 solves the issue for you too?

from crun.

It solves. Thanks for the fix.

from crun.