https://blue-build.org/ logo
I can't use rechunker in GitLab?
# questions
l
I'm trying GitLab this time instead of GitHub. While rechunker seems to work fine in GH side, I can't say the same for GitLab. https://gitlab.com/vedaproject/vedaos/-/jobs/11020875701#L171 Isn't it trying to open yet another Docker instance on top of Docker-Docker?
a
message has been deleted
l
I'll probably stick with github for now, idk what I should do
g
Ok yeah I've been running into that too
I haven't been able to figure out what's causing it
I thought maybe it's my runners, but looks like it happens on Gitlab's own runners too
l
so it's not just with rechunk then?
g
No it's only running podman/buildah as the driver
Docker works fine
But we can't do rechunk with docker
l
I'm not very technical, is there something that needs to be done in ci config file so in my case it will work just fine, or I have to like build it first in bluebuild, rechunk it afterwards and then push it to registry, if there's a way to do it?
g
No this is a bug I'd have to figure out. It might be something missing in the image, I'm not entirely sure
I just thought it was my setup so I didn't think too much of it
But seeing you're also having this issue running on a gitlab hosted runner tells me it's something else
l
yeah idk, all I did is took a sample file from cli readme, found a env variable to also do a rechunk, and then pushed it to repo
g
You can build fine without rechunk in Gitlab if you don't want to move to Github
l
since without rechunk it does build just fine, but in this case I will lose a benefit of having smaller updates 😕
g
Yeah... I'll have to spend some time diagnosing
Mind [creating an issue](https://github.com/blue-build/cli/issues/new) so I have something to track?
l
yeah no problem, I'll do it later
g
Thanks!
It might be a bit before I get to this, currently working on another feature
2 Views