Scott Giminiani

Great! Thanks for the quick reply, @ctalledo. I believe I've found a temporary workaround. For my particular use case at least. I'm mounting `docker.sock` on outer-most container. Inside this I...

Regarding your first comment, yes that's all just about correct. Just to make sure we're on the same page though, the jobs themselves are running _from_ the CI container but...

Finished reading the gitlab post. It seems that this post calls attention to the problem I mentioned above: > But there is a drawback: > >- For CI jobs that...

@ctalledo I was perusing the Sysbox release notes (my favorite pastime) and I came across [sysbox-in-docker](https://github.com/nestybox/sysbox/blob/master/sysbox-in-docker/README.md). I think I roughly get the idea, but was wondering if you could expand...

Thanks for the explanation. It would seem in both cases the inner containers would be strongly isolated since they're running with Sysbox, but it seems like the sysbox-in-docker is perhaps...

Just ran into this issue. It's been 5 years after the initial report or even last comment so I wanted to bring attention to this again. Thank you for the...

I see a lot of discussion around fixes for this which is appreciated. However, does anyone know _why_ this broke suddenly? I haven't changed anything within my project.

@mikehardy I don't believe `+` is valid syntax for version ranges. Unless you mean in the android `build.gradle`? In which case we still only have absolute versions specified. We do...

@mikehardy Thanks, that makes sense. I'm a little worried about making the `androidXCore = "1.6.0"` change as I don't really understand what it does and I don't want it to...

Thanks, I was trying to do this before but didn't realize I needed to prepend the gradle dependencies task with `app`.