To whom it may concern I would like to include the build command for RockyLinux images by Diskimage-builder in the Ironic documentation, but does the documentation need that information? https://docs.openstack.org/ironic/latest/user/creating-images.html With the following command, I successfully built an OS image of RockyLinux for Ironic. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init growroot -a arm64 -o rocky_ironic If the documentation requires the command, then I will write the command in the documentation. Best regards, Junya Noguchi -----Original Message----- From: Noguchi, Junya/野口 惇矢 Sent: Tuesday, January 28, 2025 7:12 PM To: 'Clark Boylan' <cboylan@sapwetik.org>; 'neil@shrug.pw' <neil@shrug.pw>; 'openstack-discuss@lists.openstack.org' <openstack-discuss@lists.openstack.org> Subject: RE: [ironic]About the OS supported by Diskimage-builder Dear Mr. Boylan Thank you for your answer. All disk space is now available using an image built with the addition of a growroot element. -----Original Message----- On Wed, Jan 22, 2025, at 1:53 AM, Junya Noguchi (Fujitsu) wrote:
Dear Mr. Hanlon
RHEL should be working fine -- we build Rocky Linux images in DIB and they're used in several projects including OSA and Kolla and I maintain them (by defacto ownership). Could you please provide the command you used? Also, can I use the image built by this method in bare metal?
I built the Rocky Linux OS image with the following command. $ disk-image-create rocky-container vm dhcp-all-interfaces block-device-efi openssh-server cloud-init -a arm64 -o rocky_ironic When I deployed a VM with OpenStack using the OS image created with this command, the root volume was allocated only 1.2GB of space. This problem also occurred when deploying baremetal in Ironic. -------------------------------------------------------------------------------- Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 126G 0 126G 0% /dev/shm tmpfs 51G 19M 51G 1% /run /dev/sdb3 1.2G 857M 232M 79% / /dev/sdb1 549M 7.3M 542M 2% /boot/efi tmpfs 26G 0 26G 0% /run/user/1000 ---------------------------------------------------------------------- ----------
If you know the cause of this problem, please let me know.
You either need to include the growroot element [0] which will install tooling to dynamically grow the rootfs on first boot or use explicit disk layout configuration [1] to produce an image with all of the filesystems in the sizes you expect them to be. The second option will produce larger images and you'll be more limited in where you can boot them. [0] https://docs.openstack.org/diskimage-builder/latest/elements/growroot/README... [1] https://docs.openstack.org/diskimage-builder/latest/user_guide/building_an_i...
Best regards, Junya Noguchi