https://blue-build.org/ logo
Unable to install from FCOS - No space left on dev...
# questions
m
Hey y'all, Im pretty new to this but I installed FCOS using [their docs](https://docs.fedoraproject.org/en-US/fedora-coreos/bare-metal/), then had a pretty basic butane file (below), rebooted and FCOS looked fine. I then ran
bootc switch ghcr.io/blue-build/base-images/fedora-cosmic-nvidia
and when i rebooted saw that the
ostree-boot-complete
service failed. The log said it was out of space somehow 🤔 I ran a
df -h
and everything looks fine butane:
Copy code
variant: fcos
version: 1.4.0
passwd:
  users:
    - name: matt
      ssh_authorized_keys:
        - <redacted>
      password_hash: "<redacted>"
      groups:
        - wheel
        - sudo
        - docker

storage:
  files:
    - path: /etc/hostname
      mode: 0644
      contents:
        inline: ludd
systemd:
  units:
    - name: docker.socket
      enabled: true
      contents: |
        [Unit]
        Description=Docker Socket for the API
        PartOf=docker.service

        [Socket]
        ListenStream=/var/run/docker.sock
        SocketMode=0660
        SocketUser=root
        SocketGroup=docker

        [Install]
        WantedBy=sockets.target
Hmmm, is there a chance this is because Im coming from Fedora Core OS instead of one of the "Atomic" branded ones like Fedora Cosmic Atomic? Ill give that a shot
j
It might be a problem where the boot partition is not big enough. I don't know what FCOS starts with, but for the atomic desktops you have 2 or 4 gbs nowadays, which is needed when you want multiple different snapshots. It can't rebase without space for the boot entries and those include some parts of the system. Not 100% sure if its that, but I have that issue on my desktop where I can't pin a snapshot, because then I end up with too large of a boot partition, since my install is from a time where it was only 1gb large and that is not enough
I think especially Nvidia branches, which include the kernel module in there are quite large
Yes, that is a known issue @matt.monahan : https://github.com/coreos/fedora-coreos-tracker/issues/1465 You probably have to reinstall from a different system or resize the partitions somehow (although that's probably difficult to get correct)
m
Ah cool, thanks!
That worked perfectly 🙂
a
message has been deleted
x
i just happened to run into the same issue! except on a pre-existing coreos system
6 Views