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

Allow to manage existing podman machine cpu/memory/disk through cli #13633

Closed
benoitf opened this issue Mar 24, 2022 · 1 comment · Fixed by #13953
Closed

Allow to manage existing podman machine cpu/memory/disk through cli #13633

benoitf opened this issue Mar 24, 2022 · 1 comment · Fixed by #13953
Assignees
Labels
In Progress This issue is actively being worked by the assignee, please do not work on this at this time. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine

Comments

@benoitf
Copy link
Contributor

benoitf commented Mar 24, 2022

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind feature

Description

As a user, you start a podman machine (probably using defaults)

Then at some point, you want to increase the memory or cpu or even the disk size
Or also decrease the settings because you want to adjust to your needs.

But this is not possible easily today.

podman machine set command allows only to update --rootful option

you may delete and recreate a machine but then you're losing all containers/existing images so this is not an expected behaviour.

It seems to be possible to tweak $HOME.config/containers/podman/machine/qemu/podman-machine-default.json by editing CPUs and smp parameter for the cpu but from a user point of view, we shouldn't edit qemu files.

Steps to reproduce the issue:

  1. Create and start a podman machine

  2. Wants to tweak cpu/memory/disk settings

Describe the results you received:

not possible through cli

Describe the results you expected:

it should be possible to do for example

podman machine set --cpus=2
podman machine set --disk-size=20
podman machine set --memory=4096

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

4.0.2

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)

Yes/No

Additional environment details (AWS, VirtualBox, physical, etc.):

@openshift-ci openshift-ci bot added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 24, 2022
@Luap99
Copy link
Member

Luap99 commented Mar 24, 2022

Disk could be difficult because we would need to change the file system size as well.

The other ones should be easy to implement.

@Luap99 Luap99 added the machine label Apr 4, 2022
@ashley-cui ashley-cui self-assigned this Apr 8, 2022
@ashley-cui ashley-cui added the In Progress This issue is actively being worked by the assignee, please do not work on this at this time. label Apr 19, 2022
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 20, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
In Progress This issue is actively being worked by the assignee, please do not work on this at this time. kind/feature Categorizes issue or PR as related to a new feature. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. machine
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants