Hello, while the ppc64le file Fedora-Cloud-Base-Generic-41-1.4.ppc64le.qcow2 contains fedora user in /etc/passwd, the x86_64 doesn't. Is this expected?
Fedora-Cloud-Base-Generic-41-1.4.ppc64le.qcow2
fedora
The same here: https://kojipkgs.fedoraproject.org/compose/cloud/latest-Fedora-Cloud-41/compose/Cloud/x86_64/images/Fedora-Cloud-Base-Generic-41-20241113.0.x86_64.qcow2
><fs> cat /etc/passwd root:x:0:0:Super User:/root:/bin/bash bin:x:1:1:bin:/bin:/usr/sbin/nologin daemon:x:2:2:daemon:/sbin:/usr/sbin/nologin adm:x:3:4:adm:/var/adm:/usr/sbin/nologin lp:x:4:7:lp:/var/spool/lpd:/usr/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt mail:x:8:12:mail:/var/spool/mail:/usr/sbin/nologin operator:x:11:0:operator:/root:/usr/sbin/nologin games:x:12:100:games:/usr/games:/usr/sbin/nologin ftp:x:14:50:FTP User:/var/ftp:/usr/sbin/nologin nobody:x:65534:65534:Kernel Overflow User:/:/usr/sbin/nologin tss:x:59:59:Account used for TPM access:/:/usr/sbin/nologin dbus:x:81:81:System message bus:/:/sbin/nologin systemd-oom:x:999:999:systemd Userspace OOM Killer:/:/usr/sbin/nologin systemd-coredump:x:998:998:systemd Core Dumper:/:/usr/sbin/nologin systemd-network:x:192:192:systemd Network Management:/:/usr/sbin/nologin systemd-resolve:x:193:193:systemd Resolver:/:/usr/sbin/nologin systemd-timesync:x:997:997:systemd Time Synchronization:/:/usr/sbin/nologin unbound:x:996:996:Unbound DNS resolver:/var/lib/unbound:/sbin/nologin polkitd:x:114:114:User for polkitd:/:/sbin/nologin sssd:x:995:995:User for sssd:/run/sssd/:/sbin/nologin dhcpcd:x:994:994:Minimalistic DHCP client:/var/lib/dhcpcd:/usr/sbin/nologin sshd:x:74:74:Privilege-separated SSH:/usr/share/empty.sshd:/usr/sbin/nologin chrony:x:993:993:chrony system user:/var/lib/chrony:/sbin/nologin
There's also a different volume layout between x86_64 vs ppc64le:
/dev/sda1: unknown /dev/sda2: ext4 /dev/sda3: btrfs btrfsvol:/dev/sda3/root: btrfs btrfsvol:/dev/sda3/home: btrfs btrfsvol:/dev/sda3/var: btrfs
vs.
><fs> list-filesystems /dev/sda1: unknown /dev/sda2: vfat /dev/sda3: ext4 /dev/sda4: btrfs btrfsvol:/dev/sda4/root: btrfs btrfsvol:/dev/sda4/home: btrfs btrfsvol:/dev/sda4/var: btrfs
```
The x86_64 image is a hybrid BIOS+UEFI boot image, so it will have a different layout from a PowerPC PReP boot image.
As for the fedora user, it's supposed to be created by cloud-init, so it is supposed to exist after it boots up...
Ah, makes sense. Sorry for the noise then - I must be doing something wrong then.
Metadata Update from @praiskup: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.