28 Replies
here @Robert (p5)
so, yeah, as my normal silverblue user
I ran:
podman build -f Containerfile --build-arg BASE_TAG=40 -t lumina:40 and did not have the tar permissions issue
but, i have actually seen another weird issue with podman build which is only repoducible on some users and not othersDoes your build contain the --no-same-permissions tar flag? It will depend on when you pulled the code
it does not contain that, i pulled right before you added
2d3236a42ad08189345ca1b3b1c95c57edf57056
okay.. So somehow this is a Podman / Buildah bug which is fixed in newer versions?
I DID have to comment out the ptyxis stuff to get a build though>
becuase i was getting this failure and it stopped the build
error: Request to reinstall exact base package versions: gtk4 libadwaitaYeah, that ptyxis stuff is fixed on the PR branch. Added a flag to only install those two deps on F39
want me to try your branch?
It shouldn't really make a difference I don't think. Unless Ptyxis is causing the issues, which seems unlikely
agreed
so, the other problem i mentioned...
as my user on my main (custom silverblue) machine, i'm unable to do a build of akmods or hwe which uses the surface kernel...
but it does work on my bazzite machine
i need to test again (i've lost track) but it may even work on my main machine, but with a different user
Kinda wanting to switch to Docker. We may have less of these bugs, but it may also not fix anything
heh
it does feel like there's something environmental bleeding into the build container
but hard to troubleshoot
yeah the whole thing is odd
using --no-same-permissions is a shot in the dark, even if it works I'll be confused
because it will use the root user's umask
which is wonky
yeah, so i've just confirmed, on my weird problem i mentioned... it's user specific... another user on my main machine CAN build surface image with the custom kernel, just not my main user
@bsherman do both the users have the same umask?
and do they both have the same permissions?
as in neither is root 😅
right, both are users with wheel group membership, but not root
and same umask?
yes, both have 0022
😵💫 super weird
Screw it. Switching to building inside Docker and Buildx so hopefully there's more consistency. Builds will be slower.
@Robert (p5) did the flag work tho
the tar --no-same-permissions flag? i haven't tested that locally
it really doesn't feel like that's the problem though
probably not
I'm unable to build locally since I'm on my locked down MacBook, and GitHub Actions is having issues right now. Will try the workflow again
oh github actions
joy
It always happens when I'm trying to do something. On the rest days, no availability issues
i feel ya
GitHub
GitHub - nektos/act: Run your GitHub Actions locally 🚀
Run your GitHub Actions locally 🚀. Contribute to nektos/act development by creating an account on GitHub.
and actually, with act, all stuff runs in container, but buildah/podman can't work
but... buildx can