Visual Studio 2022 push to custom docker container stopped working after changing image name

Question

I have a visual studio .pubxml for publish into a custom docker container with a dockerfile.

It's working well, the build generates the image and then the push is done correctly.

The problem is that I need to change the image name to push, by default it takes the project name.

<Project>
<PropertyGroup>
    <WebPublishMethod>Custom</WebPublishMethod>
    <DockerPublish>true</DockerPublish>
    <RegistryUrl>https://myUrl</RegistryUrl>
    <UserName>XXXXX</UserName>
    <PublishImageTag>latest</PublishImageTag>
    <PublishProvider>ContainerRegistry</PublishProvider>
    <LastUsedBuildConfiguration>Release</LastUsedBuildConfiguration>
    <LastUsedPlatform>Any CPU</LastUsedPlatform>
    <_TargetId>DockerCustomContainerRegistry</_TargetId>
    <!--<DockerfileBuildArguments>-t NEWNAME</DockerfileBuildArguments>-->
    <DockerfileTag>NEWNAME</DockerfileTag>
</PropertyGroup>

This is my .pubxml, with the DockerfileBuildArguments -t NEWNAME or with the DockerfileTag NEWNAME. The image that is generated is correct. But when visual studio try to do the push is still searching for the old named image (that is not generated now)

docker push PROJECTNAME:latest

But I want visual studio to do

docker push NEWNAME:latest

and I'm getting this error cause the image with the PROJECTNAME is not generated now:

Microsoft.WebTools.Azure.Publish.Docker.DockerCommandException: Running the docker.exe tag command failed.
Error response from daemon: No such image: PROJECTNAME:latest

Any ideas of how I can change that?

Thanks!

Nathan Carlson - MSFT · Answer 1 · 2023-04-13T22:17:12.637

1

<DockerfileTag>NEWNAME</DockerfileTag> needs to go into the project file not the publish profile.

edited Apr 13 '23 at 22:17

answered Apr 06 '23 at 22:41

Nathan Carlson - MSFT

399
2
6

Hi, I also tried that and it's not working, if you see in the question the DockerfileBuildArguments is commented – Dani Hernandez Apr 11 '23 at 07:05
In the question you've commented out `-t NEWNAME` the fix is to do `-t PROJECTNAME` – Nathan Carlson - MSFT Apr 12 '23 at 21:32
yes, cause i need a NEWNAME image, i dont want a PROJECTNAME image – Dani Hernandez Apr 13 '23 at 13:40
Egg on my face, I just triple checked and the work-around fixes the build error, but pushed the wrong image. You do need to put the property DockerfileTag into the project file. – Nathan Carlson - MSFT Apr 13 '23 at 22:18

Visual Studio 2022 push to custom docker container stopped working after changing image name

1 Answers1