Michael Kriese

Gitlab supports multiple nested groups, so an image repo can be have more that three parts, eg `registry.gitlab.test/group/subgroup/subsubgroup/image`. I think we should treat this image as `registryUrl=https://registry.gitlab.test` and `depName=group/subgroup/subsubgroup/image`. This...

OK, then i'm fine with it. So we extract `gitlab.example.com/groupname/dependency_proxy/containers/library/alpine:latest` as - `registryUrls=https://gitlab.example.com/groupname/dependency_proxy/container` - `depName=alpine` - `lookupName=library/alpine` And when combined with `registryUrls: [ "https://some.registry.com/project" ]` package rule renovate would resolve...

Yes, was a typo, fixed it

> In this scenario we'd never extract `registryUrl` from an image string. Don't like that, as I've a lot images who are not availabe on hub, so configure hostrules for...

Ok

As far as i understand the docs, we can use a simple regex to parse the deps.

I think it should use Gradle wrapper.

Can you build a small public reproduction repo. So we can debug this. It's also important how are you running renovate. Currently only binarySource=docker is able to respect constraints.

I've checked the code now. So currently the `postUpgrade` tasks are run as direct child without any docker container. It also don't have any concept of `constraints`, so it's not...

yes, as we don't pass any docker args to exec checked here: https://github.com/renovatebot/renovate/blob/5d99ff9862bac803dcea4e6ded5f3fec34abccfc/lib%2Futil%2Fexec%2Findex.ts#L126-L141