你可以试试:

services:
  nameis:
    container_name: hi_my
    build: .
    image: hi_my_nameis:v1.0.0

我想补充一点，您还可以通过环境变量或.env文件管理标记版本。

https://docs.docker.com/compose/environment-variables/#the-env-file

出口标签= 1.11

例子:

version: '3.3'
services:

  baggins.api.rest:
    image: my.image.name:${TAG}
    build:
      context: ../..
      dockerfile: app/Docker/Dockerfile.release
    ports:
      ...

Docker-compose配置来验证

在我的ci管道中，我的第一个构建被标记为用于运行测试的丢弃值。然后，我将标记更改为latest并重新构建(几乎是即时的，因为它都是缓存的)，然后推到注册表。

看起来docs/tool已经更新了，你现在可以把image标签添加到你的脚本中了。这对我来说很成功。

例子:

version: '2'
services:

  baggins.api.rest:
    image: my.image.name:rc2
    build:
      context: ../..
      dockerfile: app/Docker/Dockerfile.release
    ports:
      ...

https://docs.docker.com/compose/compose-file/#build

它适合我:https://docs.docker.com/build/customize/bake/compose-file/#specification

services:
  backend:
    build:
      context: ./backend
      dockerfile: Dockerfile
      tags:
        - spring-postgres:1.0
        - spring-postgres:latest
    ports:
      - 8080:8080

然后运行docker compose build——no-cache output，如下所示:

> docker compose build --no-cache
[+] Building 192.9s (13/13) FINISHED
 => [internal] load build definition from Dockerfile                                                                                                              0.0s 
 => => transferring dockerfile: 457B                                                                                                                              0.0s 
 => [internal] load .dockerignore                                                                                                                                 0.0s 
 => => transferring context: 2B                                                                                                                                   0.0s 
 => [internal] load metadata for docker.io/library/eclipse-temurin:17-jre-focal                                                                                   0.0s 
 => [internal] load metadata for docker.io/library/maven:3.8.5-eclipse-temurin-17                                                                                 0.0s 
 => [builder 1/5] FROM docker.io/library/maven:3.8.5-eclipse-temurin-17                                                                                           0.0s 
 => CACHED [stage-1 1/3] FROM docker.io/library/eclipse-temurin:17-jre-focal                                                                                      0.0s 
 => [internal] load build context                                                                                                                                 0.0s 
 => => transferring context: 1.05kB                                                                                                                               0.0s 
 => CACHED [builder 2/5] WORKDIR /code                                                                                                                            0.0s 
 => [builder 3/5] COPY pom.xml pom.xml                                                                                                                            0.0s 
 => [builder 4/5] COPY src .                                                                                                                                      0.0s 
 => [builder 5/5] RUN mvn clean -DskipTests -T 2C -X -am install                                                                                                192.5s 
 => [stage-1 2/3] COPY --from=builder /code/target/*.jar app.jar                                                                                                  0.0s 
 => exporting to image                                                                                                                                            0.0s 
 => => exporting layers                                                                                                                                           0.0s 
 => => writing image sha256:a5827124abc899efcfbc8db150f72f5ff8034d1ab93418dee5c15525ae4e42a1                                                                      0.0s 
 => => naming to docker.io/library/spring-postgres-backend                                                                                                        0.0s 
 => => naming to docker.io/library/spring-postgres:1.0                                                                                                            0.0s 
 => => naming to docker.io/library/spring-postgres:latest                                                                                                         0.0s 

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them

以上控制台输出spring-postgres:1.0和spring-postgres:最新

原答案15年11月20日:

截至今天，没有特定标记的选项。Docker compose只是发挥它的魔力，像你看到的那样分配一个标签。在你调用docker-compose之后，你总是可以有一些脚本调用docker tag <image> <tag>。

现在有一个如上所述的选项

build: ./dir
image: webapp:tag

如果你指定了image和build，那么Compose用image中指定的webapp和可选标签来命名构建的图像:

build: ./dir
image: webapp:tag

这将导致一个名为webapp的图像和标记标签，从./dir构建。

https://docs.docker.com/compose/compose-file/#build