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

the extra disk (nvme, etc) should be mounted on /var/lib/containers on bastion #324

Open
iranzo opened this issue Mar 9, 2023 · 1 comment

Comments

@iranzo
Copy link
Contributor

iranzo commented Mar 9, 2023

On bastion host, specially when holding a registry, the root hard drive can get filled.

If the host has extra disks, like nvme, they should be made ready on /var/lib/containers so that system is getting root disk filled

@akrzos
Copy link
Member

akrzos commented May 8, 2023

I think we should just document how to setup a separate disk to host your disconnected registry. I have ran into this myself and have a few steps to quickly resolve this issue:

  1. Tear down any podman pods on bastion
  2. mv /opt /opt2
  3. parted /dev/nvme0n1 (Or whatever extra disk you are using)
  4. (parted) mklabel
  5. (parted) unit s
  6. (parted) mkpart primary xfs 0% 100%
  7. (parted) quit
  8. mkfs.xfs /dev/nvme0n1p1
  9. mkdir opt
  10. lsblk --fs /dev/nvme0n1p1
  11. vi /etc/fstab
  12. systemctl daemon-reload
  13. mount /opt
  14. rerun setup-bastion to bring podman pods back up

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

No branches or pull requests

2 participants