[bug] When the image repository address selected for pipeline construction is inconsistent with the 'from' address in the service's dockerfile, it will result in the inability to pull the underlying image of 'from'

[ItBayMax]

What happened? When the image repository address selected for pipeline construction is inconsistent with the 'from' address in the service's dockerfile, it will result in the inability to pull the underlying image of 'from'

What did you expect to happen? The build tasks in the pipeline should automatically log in to the from base image repository defined in Dockerfile, as the base image and the image built by the project may not be located in the same image repository.

How To Reproduce it(as minimally and precisely as possible) 1、The from address in the dockerfile of the project service is: 192.168.100.100:3000/public 2、The task address of the assembly line is: 192.168.100.200:3000/project 3、At this time, it is not possible to pull the image from Dockerfile because the image repository selected by the build task in the pipeline will be used for login 4、However, if the image repository parameters in the pipeline construction task are changed to be consistent with those in the dockerfile, it will also result in the inability to push the constructed images

Versions Used zadig: 3.0 kubernetes: v1.22.12， KubeSphere 3.4.1

[PetrusZ]

Did you build from local clustuer or other clustuers?

[leozhang2018]

Since there has been no response from the user for an extended period, we will proceed to close this issue. If you have any further questions or need assistance, feel free to reopen or create a new issue.