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

Show container size when running list command #1026

Open
Jacalz opened this issue Mar 20, 2022 · 9 comments · May be fixed by #1035
Open

Show container size when running list command #1026

Jacalz opened this issue Mar 20, 2022 · 9 comments · May be fixed by #1035
Labels
1. Feature request A request for a new feature 2. Host Realm The issue is related to what happens on the host machine where Toolbox is executed 5. Good First Issue Good for newcomers
Milestone

Comments

@Jacalz
Copy link

Jacalz commented Mar 20, 2022

Is your feature request related to a problem? Please describe.

I want to be able to know the size of my installed containers. If you have many different toolboxes with different configurations like different packages, different distributions and different installed packages it would be good to be able to compare sizes between them.

Describe the solution you'd like

A column with size when running toolbox list.

Describe alternatives you've considered

A flag to pass to the toolbox list command to show sizes.

Additional information

Related to #752.

@Jacalz Jacalz added the 1. Feature request A request for a new feature label Mar 20, 2022
@HarryMichal HarryMichal added 5. Good First Issue Good for newcomers 2. Host Realm The issue is related to what happens on the host machine where Toolbox is executed labels Mar 20, 2022
@HarryMichal
Copy link
Member

Sounds like a reasonable request. Patches are welcome :).

Will require adding a new cmd option, plumbing it down to podman.GetContainers, process the received JSON and present it. Just check when the option/information became available so that we don't have to raise our minimal Podman support.

@Jacalz
Copy link
Author

Jacalz commented Mar 20, 2022

Cool. I'm a bit weighed down with university studies at the moment, but I might consider it some time in the future :)

@HarryMichal
Copy link
Member

I know the feeling :). The incentive was meant for all potential contributors.

@arejula27
Copy link

Is this a issue for newcommers?

@Jacalz
Copy link
Author

Jacalz commented Mar 21, 2022

I think so. From what I can see, it should be relatively straight forward to implement.

@HarryMichal HarryMichal added this to the Release 0.2.0 milestone Mar 21, 2022
@Parth576
Copy link

Parth576 commented Apr 4, 2022

Can I try working on this? Also, wanted to ask if we can build & install toolbox within a toolbox?

@Jacalz
Copy link
Author

Jacalz commented Apr 4, 2022

Can I try working on this?

From my point of view, yes. I haven’t started working on anything :)

@arejula27
Copy link

I wanted to do It but currently i have a los of university work so yes u can do it from muy pov

@HarryMichal
Copy link
Member

Can I try working on this?

Of course 👍.

Also, wanted to ask if we can build & install toolbox within a toolbox?

It is buildable and installable but there's no point in running it in a toolbx because Toolbx sends commands from within a container to the host. Instead, build it in a toolbx and run on the host.

@Parth576 Parth576 linked a pull request Apr 6, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. Feature request A request for a new feature 2. Host Realm The issue is related to what happens on the host machine where Toolbox is executed 5. Good First Issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants