Cannot Rebase to Local Image
Running
sudo bluebuild rebase ./recipes/recipe.yml
results in the following error.
Rebasing onto images built via the github workflow work just fine.
21 Replies
Interesting, I've not see that before
Mind sending a link to your recipe?
GitHub
GitHub - dkolb/bazzite-dkub: Personalized Bazzite Image built using...
Personalized Bazzite Image built using BlueBuild. Based off of bazzite-gnome. - dkolb/bazzite-dkub
Nothing looks off to me there..
How many times have you tried running that command? Does this happen every time?
Yes, every time.
LIke I said, if I build it in github, push, and then update to the published image it works fine so I haven't been bothered by it too much, it just slows me down. Lol.
The image works fine if I just build and run it like
podman run --rm -it localhost/bazzite-dkub:latest /bin/sh
to poke around and check files, etc.I'll have to try running my builds locally and see what happens
It's just the rebase onto the archive that blows up.
Have you already rebased onto it and you're trying to do another update?
Cause if that's the case you would use
bluebuild upgrade
. Both of those commands are going to be replaced with bluebuild switch
in the v0.9
release soonOk
Had to check
I thought the answer was no, lmao but I didn't know if you mean the image in general or the archive. 😂
This might take longer than a few minutes. Mind creating an issue for it? https://github.com/blue-build/cli/issues/new
GitHub
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
Sure.
Thanks! I'm currently working on getting recipe validation working and I'm so close
It's very rare that I find an error message google has no clue about. 😂
I wonder if it's podman specific?
It's definitely an error regarding rpm-ostree for sure
Maybe
Do you have podman installed and not docker?
Yeah this is a bazzite based image.
Just asking, I have docker installed on my image and the tool will select a container runtime on start
Ah.
I figured podman would be good enough lol. Might mess around and install docker later and see if that works.
I gotta run some errands today and date night with spouse. Will try the run around with docker tomorrow and update the issue. ^_^
Have fun!
Confirmed this is a podman specific issue.
Thanks for confirming. I'll try to work on that this week.