Get network access to local service when pulling Docker images

this question is bound to Drone Cloud service.

There were questions in the past about building Docker images in one step and then using this image to run container in another step without unnecessary network usage with uploading and downloading it. And these have the answer that it is not possible.

But enough time passed and trying to reinvent my own wheel, I have been thinking if I somehow cannot make the services network accessible to the Drone executor when specifying from where the image should be downloaded.

I can of course build the image and then upload it to a Docker registry running as a local service to the pipeline, but trying to download this image as a step container ends on DNS error - which is understandable.

However, I have to ask - couldn’t this be somehow hacked around?