The machine-os-content fails to build #15
Comments
aleskandro
added a commit
to aleskandro/okd-machine-os
that referenced
this issue
Oct 18, 2022
…nd the okd-payload-pipeline Refers okd-project/okd-payload-pipeline#15
aleskandro
added a commit
to aleskandro/okd-machine-os
that referenced
this issue
Oct 18, 2022
…nd the okd-payload-pipeline Refers okd-project/okd-payload-pipeline#15
aleskandro
added a commit
to aleskandro/okd-machine-os
that referenced
this issue
Oct 18, 2022
…nd the okd-payload-pipeline Refers okd-project/okd-payload-pipeline#15
vrutkovs
pushed a commit
to vrutkovs/okd-machine-os
that referenced
this issue
Nov 9, 2022
…nd the okd-payload-pipeline Refers okd-project/okd-payload-pipeline#15
vrutkovs
pushed a commit
to vrutkovs/okd-machine-os
that referenced
this issue
Nov 9, 2022
…nd the okd-payload-pipeline Refers okd-project/okd-payload-pipeline#15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just a reminder to address the discussion in #14
Due to the changes in the
artifactsimage that now put the rpms in the /srv/repo/$arch dir, the okd-machine-os Dockerfile should be updated to address this new behavior. This work could also be part of making the new dockerfiles for hyperkube, cli (and artifacts) upstream.cc @vrutkovs
The text was updated successfully, but these errors were encountered: