Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend the output format with a tree view #75

Closed
behouba opened this issue Jun 19, 2023 · 1 comment · Fixed by #76
Closed

Extend the output format with a tree view #75

behouba opened this issue Jun 19, 2023 · 1 comment · Fixed by #76

Comments

@behouba
Copy link
Collaborator

behouba commented Jun 19, 2023

Currently, the output format of checkpointctl is in a table format. However, due to the limitations of horizontal space and the need to display multiple checkpoints, it would be beneficial to add a tree view format. This offers several advantages:

  • The tree format takes advantage of unlimited vertical space, which is more suitable for displaying detailed information.
  • The tree format can be used with multiple checkpoints, allowing for the presentation additional details for each checkpoint.
  • A built-in terminal pager, (e.g: systemctl status), would enhance the usability of the output.

Here's an example of how the output could look:

containername
├── IMAGE: registry/name:latest
├── ID: 209872364234
├── RUNTIME: runc
├── CREATED: 2023-05-19T08:44:58.018444733Z
├── ENGINE: CRI-O
├── IP: 10.88.0.11
├── CHECKPOINT SIZE:
├── ROOT FS DIFF SIZE:
├── NAMESPACES:
│   ├── UTSNS
│   │   ├── NODENAME: hostname01
│   │   └── DOMAINNAME: (none)
│   └── IPC
└── PROCESSES
    └── [1]  bash
        ├── [7]  counter.py
        └── [8]  tee

Suggested by @adrianreber

@rst0git
Copy link
Member

rst0git commented Jun 19, 2023

It might be useful to also be able to render the output in a JSON format (e.g., similar to podman inspect). This would enable easier integration with other tools to further process the output of checkpointctl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants