-
Notifications
You must be signed in to change notification settings - Fork 100
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
k3s no space left on device #2682
Comments
Yes, confirmed, your persistent is 55Mb only, but the partition is 228Gb. That means that the growpart worked but the resize2fs didnt and it left it in a broken state. You can probably workaround this by running |
I know and i already did it as mentioned in
But, i think an persistent solution via bootstrap process would be nice.
Not rlly. Just the next issue as mentioned in
But since it is a different problem, i could move it to a new issue. Any thoughts? |
Sounds good. selinux should work out of the box in leap IIRC, unless it now requires some packages like ubuntu does with the new 15.6 release, so it makes sense to have a card to track that. Thanks! |
Just found that cryptsetup is only installled on amd64 in our dockerfiles, which causes dracut issues. just happen that the required binaries for the persistent expansion are just after the cryptsetup binary, so maybe dracut is reaching cryptsetup, hitting the error and not installing the needed binaries in the initramfs??? Testing this... |
Seems like the issue is still there.
|
thanks for confirmation @kaiehrhardt |
@mauromorales can you confirm that this works as expected with the latest version? @kaiehrhardt can you also share the output of blkid and lsblk? |
It seems to be working correctly with the latest release. I'm using an SD card to install, and I can successfully see the different pods running on k9s, and no fatal issues on k3s logs:
I will close the issue for now, but you are welcome to re-open @kaiehrhardt if there's something that I missed testing here |
Kairos version:
CPU architecture, OS, and Version:
Logs
df -h
lsblk
cat /run/immucore/rootfs_stage.log
Any ideas?
Same as #1928?
after #1599 (comment)
edit
moved following context to #2689:
journalctl -xefu k3s
I could open an additional issue if you like. -> done
The text was updated successfully, but these errors were encountered: