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

Rewrite diskspace wiki page in a more generic way (FAQ) #690

Closed
gbraad opened this issue Oct 5, 2019 · 4 comments
Closed

Rewrite diskspace wiki page in a more generic way (FAQ) #690

gbraad opened this issue Oct 5, 2019 · 4 comments
Labels
kind/documentation Documentation issues. kind/task Workable task points/1 priority/major status/stale Issue went stale; did not receive attention or no reply from the OP

Comments

@gbraad
Copy link
Contributor

gbraad commented Oct 5, 2019

the current page https://github.com/code-ready/crc/wiki/Disk-space-issue-with-beta-5-release is written for beta5, and therefore includes a static password and a node reference that does not exist in newer deployments. we should rewrite this in a more generic way that gets the kubeadmin password and the master node identity. this way we can include it as a FAQ entry.

@gbraad
Copy link
Contributor Author

gbraad commented Oct 5, 2019

For linux it is easy to also describe how to enlarge the containing disk image, but how about Windows and macOS? We might need to direct them to qemu-img tooling for macOS and the management interface/powershell on Windows.

@gbraad
Copy link
Contributor Author

gbraad commented Oct 10, 2019

See #127 (comment) for more info. This needs to be documented in some form before we can add a command.

@cfergeau
Copy link
Contributor

Regarding disk resizing, I don't know how to do it on OS where virt-resize don't run. Maybe through qemu-img and running some commands in the running VM?

@stale
Copy link

stale bot commented Feb 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the status/stale Issue went stale; did not receive attention or no reply from the OP label Feb 11, 2020
@stale stale bot closed this as completed Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Documentation issues. kind/task Workable task points/1 priority/major status/stale Issue went stale; did not receive attention or no reply from the OP
Projects
None yet
Development

No branches or pull requests

2 participants