Features Request: automatic stop of the container when exiting app inside container and status refresh

[NotMainstream]

Hello, you don t have a Feature Request category so I can only submit it as a Bug unfortunately. It would be very useful if you can add a few features like: -daily automatic update of the containers -automatic stop of the container when exiting apps inside container -automatic status refresh so we don t have to click refresh each container in BoxBuddy every time we want to see which containers still work in the background -a clone button for the containers so we don t have to use the CLI every time -add an export/import button for the containers so we can easily move them to other machines or VMs -a size info section were we can have an overview of the containers size -RAM usage info for every container

[Dvlv]

Hello BoxBuddy is just a UI for distrobox, so I don't want to start adding anything "autonomous".

-daily automatic update of the containers

Out of scope for a UI

-automatic stop of the container when exiting apps inside container

Out of scope for a UI

-automatic status refresh so we don t have to click refresh each container in BoxBuddy every time we want to see which containers still work in the background

The status does refersh when appropriate. The problem is, to refresh the status, I have to fetch the list of all boxes again, which is somewhat expensive.

-a clone button for the containers so we don t have to use the CLI every time

Will add this to the roadmap.

-add an export/import button for the containers so we can easily move them to other machines or VMs

I had this in the old C++ version, but the problem is once you re-import a container it has an image name like localhost:my-box so the UI is then unable to parse its distro, which breaks functionality. For that reason, I won't be adding this feature again.

-a size info section were we can have an overview of the containers size

Is there a distrobox command for this? If so could you please link it.

-RAM usage info for every container

As above, I can't see how to get this information.

[NotMainstream]

Thanks for the very fast answer, I wish I would of been smart enough to be able to tell you how to see the size info and RAM usage. I could see the size of the container when I used 'distrobox-create --clone' so that might be a starting point. And for the RAM usage maybe this can be a good place to take a look: 'ps aux | grep distrobox' The 'distrobox-create --clone' works very well for cloning and BoxBuddy sees properly the new container. I`m wondering if it can be used to import/export a container to a different location or even compress it as an archive.

[VortexAcherontic]

I think in theory you can use: podman stats for ram and cpu usage of running podman containers. Don't know for Docker though so it might not work on systems using Docker.

[NotMainstream]

Thanks. I didn t knew about podman stats.

[Dvlv]

I've made #77 and #78 to track these. I'll close this issue and you can follow the new ones if you're interested.