Any idea why I can create VMs with uCore if they have 1 core 2 gb of memory and 16 storage and they fail if I add more?

uCore
1

Hello!

I am new to this and linux and I was giving proxmox a try since you can easily create vms and test stuff around, and I wanted to try ucore ublue.

Now it took me a moment to find how to use ignition files, but I think I have done so correctly, as I can boot normally both in fedora coreos VMs and also into ucore ublue if it has 1 core 2 gb of memory and 16 storage, I didn’t try too many configs because the error seemed to be irrelevant to it, but I can’t figure out why it is happening.

Let me explain, I use this file

variant: fcos
version: 1.6.0
passwd:
  users:
    - name: core
      ssh_authorized_keys:
        - ssh-ed25519 mykey
      password_hash: "myhashedpassword"
storage:
  directories:
    - path: /etc/ucore-autorebase
      mode: 0754
systemd:
  units:
    - name: ucore-unsigned-autorebase.service
      enabled: true
      contents: |
        [Unit]
        Description=uCore autorebase to unsigned OCI and reboot
        ConditionPathExists=!/etc/ucore-autorebase/unverified
        ConditionPathExists=!/etc/ucore-autorebase/signed
        After=network-online.target
        Wants=network-online.target
        [Service]
        Type=oneshot
        StandardOutput=journal+console
        ExecStart=/usr/bin/rpm-ostree rebase --bypass-driver ostree-unverified-registry:ghcr.io/ublue-os/ucore:stable
        ExecStart=/usr/bin/touch /etc/ucore-autorebase/unverified
        ExecStart=/usr/bin/systemctl disable ucore-unsigned-autorebase.service
        ExecStart=/usr/bin/systemctl reboot
        [Install]
        WantedBy=multi-user.target
    - name: ucore-signed-autorebase.service
      enabled: true
      contents: |
        [Unit]
        Description=uCore autorebase to signed OCI and reboot
        ConditionPathExists=/etc/ucore-autorebase/unverified
        ConditionPathExists=!/etc/ucore-autorebase/signed
        After=network-online.target
        Wants=network-online.target
        [Service]
        Type=oneshot
        StandardOutput=journal+console
        ExecStart=/usr/bin/rpm-ostree rebase --bypass-driver ostree-image-signed:docker://ghcr.io/ublue-os/ucore:stable
        ExecStart=/usr/bin/touch /etc/ucore-autorebase/signed
        ExecStart=/usr/bin/systemctl disable ucore-signed-autorebase.service
        ExecStart=/usr/bin/systemctl reboot
        [Install]
        WantedBy=multi-user.target

which is basically the example given on github but with 2 stuff added my ssh key and my hashed password, (and I guess I also change the version) which both work fine as I used them in other installs.

When I use the ignition file from this on a fresh VM with the fedora coreos iso in it with 6 cores 8 gb ram and 32 gb of storage it fails initially with an error
”ucore failed units : 1 ucore-unsigned-autorebase.service”

The output of “journalctl -u ucore-unsigned-autorebase.service"
gives me this

Jan 10 21:28:49 localhost.localdomain systemd[1]: Starting ucore-unsigned-autorebase.service - uCore autorebase to unsigned OCI and reboot...
Jan 10 21:28:49 localhost.localdomain rpm-ostree[1690]: Pulling manifest: ostree-unverified-registry:ghcr.io/ublue-os/ucore:stable
Jan 10 21:28:49 localhost.localdomain rpm-ostree[1690]: error: Preparing import: Fetching manifest: failed to invoke method OpenImage: pinging container registry ghcr.io: Get "https://ghcr.io/v2/": dial tcp: lookup ghcr.io: Temporary failure in name resolution
Jan 10 21:28:49 localhost.localdomain systemd[1]: ucore-unsigned-autorebase.service: Main process exited, code=exited, status=1/FAILURE
Jan 10 21:28:49 localhost.localdomain systemd[1]: ucore-unsigned-autorebase.service: Failed with result 'exit-code'.
Jan 10 21:28:49 localhost.localdomain systemd[1]: Failed to start ucore-unsigned-autorebase.service - uCore autorebase to unsigned OCI and reboot.

I cannot understand why it fails, it seems to be a connection error. I can create as many VMs with ucore ublue as I want if they are 1 core 2 gb but 2 or 6 cores fail with the same error. I create them at random, 2 small ones in a row, 2 big ones in a row, 1 small one and 1 big one, and the “bigger” ones always get this error.

The thing is, if I reboot again after this failure on the big ones, the process completes. Any idea what the issue is? The small ones complete the process on 1 reboot with no errors.

  1. Actually, what I care most is, is there any problems that could arise if I just make my vms with fedora coreos and then rebase to ucore? Like leftover files that could create problems? Because that process works without any issues.
  2. Or if even the process I described above is fine with the 2 reboots needed.
    It is just that I would like to know if there is another issue I am missing with the previous process.

Anyway, maybe I have also missed something else while explaining it. If something isn’t clear or you would like more info, please let me know.
If anyone takes the time to check this, thanks! In the end of the day, I can boot it, I guess.