Push without latest

This is a question. Is it possible to build an image, as a specific version (tag), then push it, without pushing latest?

This is what I’m having so far, and it pushes both a latest and a (substituted) ${project.version}.

<image>
    <name>company/${project.artifactId}</name>
    <alias>${project.artifactId}</alias>
    <registry>my.registry.host</registry>
    <build>
        <tags>
            <tag>${project.version}</tag>
        </tags>
        <from>java:8-jdk</from>
        ...
    </build>
</image>

I’ve tried setting the tag directly:

<name>company/${project.artifactId}:${project.version}</name>

But that just runs me into trouble:

[INFO] --- docker-maven-plugin:0.11.2:build (dockerize) @ artifactId ---
[INFO] DOCKER> Creating image [company/artifactId:1.0.8-SNAPSHOT] "artifactId"
[INFO] Copying files to E:\artifactId\provider\target\docker\company\artifactId\1.0.8-SNAPSHOT\build\maven
[INFO] Building tar: E:\artifactId\provider\target\docker\company\artifactId\1.0.8-SNAPSHOT\tmp\docker-build.tar
[INFO] DOCKER> Tagging image [company/artifactId:1.0.8-SNAPSHOT] "artifactId": 1.0.8-SNAPSHOT
[ERROR] DOCKER> could not find image: no such id: company/artifactId (Not Found: 404)

And:

[ERROR] Failed to execute goal org.jolokia:docker-maven-plugin:0.11.2:build (dockerize) on project artifactId: Unable to add tag [company/artifactId:1.0.8-SNAPSHOT] to image [company/artifactId:1.0.8-SNAPSHOT] -> [Help 1]

This may be a flaw yet into my understanding of Docker, but I’m trying to avoid latest to be pushed from every branch that is building this stuff, and we tend to represent the branches in the version name while in our CI environment. I am trying to avoid it in part because I think it has little meaning in my highly branched environment, but I’m also afraid for concurrency issues.

[rhuss]

@MichalOrlowski just on a second though: You can always do a

                        <image>
                            <name>app-name:${project.version}</name>
                            <build>
                                <dockerFileDir>${project.basedir}/module_name</dockerFileDir>
                                <tags>
                                    <tag>${envTag}</tag>
                                </tags>
                            </build>
                        </image>

This would solve your use case, as the latest results only because you haven’'t specified a tag in the name. Thinking again thats a better solution then the one I proposed above, as it works already now and is sufficiently clean enough 😉

[mohnishkodnani]

I have the same problem. Where I have multiple tags in the configuration and the latest always get pushed. Due to this when multiple jobs are running simultaneously and because we have big images , they end up failing due to the latest tag being created from multiple branches. Image xyz:latest could be pushed, but the temporary tag could not be removed and then the build fails. I dont see this problem if I only have one job running.