metal3 - updates for 0.9.1 chart #69
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "steven.hardy/Factory:metal3_091"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Align with https://github.com/suse-edge/charts/pull/173 which added some fixes to enable deployment on aarch64
This also requires updates to the ironic and IPA images, which are derived from https://build.opensuse.org/project/show/isv:SUSE:Edge:Metal3:Ironic:2024.2
The root.tar.bz2 doesn't look like it's using git-lfs for storage.
@ -10,2 +10,3 @@
RUN sed -i -e 's%^# rpm.install.excludedocs = no.*%rpm.install.excludedocs = yes%g' /etc/zypp/zypp.conf
RUN zypper --installroot /installroot --non-interactive install --no-recommends ironic-ipa-ramdisk-x86_64 python311-devel python311 python311-pip tar gawk git curl xz fakeroot shadow sed cpio; zypper -n clean; rm -rf /var/log/*
#!ArchExclusiveLine: x86_64
RUN zypper --installroot /installroot --non-interactive install --no-recommends ironic-ipa-ramdisk-x86_64 python311-devel python311 python311-pip tar gawk git curl xz fakeroot shadow sed cpio; zypper -n clean; rm -rf /var/log/*;
Those
ArchExclusiveLine
things are OBS specific to tell OBS to not try to parse the line for specific arch, it will still get executed by docker build process. You need to use a construction akin to the one inironic-image
Dockerfile here:Thanks, fixed - I will also adjust this in the next upstream release of this image
@ -129,3 +130,3 @@
<package name="kernel-default"/>
<package name="NetworkManager"/>
<package name="nm-configurator"/>
<package name="nm-configurator-030"/>
Should not use a package suffix here
@ -88,3 +93,3 @@
BuildRequires: which
BuildRequires: NetworkManager
BuildRequires: nm-configurator
BuildRequires: nm-configurator-030
Same here
b0ee84e6e1
toac32110ac1
I locally configured git-lfs and did
git rm --cached
and re-added the tarball in a new commit - how do I check if it's now using lfs or not?