URGENT actions/docker gives 404

Is it a deprication? How to achieve the same? Is there any migration documentation out there?

3 Likes

I think we can just use docker now (as “run”). Looks to solve it for me!

1 Like

However it looks like publishing to a docker registry (not the default) is broken now.

You will have to login to the registry before pushing. 

Example: 

- name: Logging in to container registry...
        env:
          DOCKER_PASSWORD: ${{ secrets.DOCKER_PASSWORD }}
          DOCKER_REGISTRY_URL: ${{ secrets.DOCKER_REGISTRY_URL }}
          DOCKER_USERNAME: ${{ secrets.DOCKER_USERNAME }}
        run: docker login -u $DOCKER_USERNAME -p $DOCKER_PASSWORD $DOCKER_REGISTRY_URL
      - name: Building Docker container...
        env:
          CONTAINER_IMAGE_NAME: ${{ secrets.CONTAINER_IMAGE_NAME }}
          DOCKER_REGISTRY_URL: ${{ secrets.DOCKER_REGISTRY_URL }}
          CSIUtilityServer: ${{ secrets.CSIUtilityServer_PROD }}
        run:
          docker build --rm --build-arg CSIUtilityServer=$CSIUtilityServer --no-cache -t $DOCKER_REGISTRY_URL/$CONTAINER_IMAGE_NAME:latest
          .
      - name: Publishing Container...
        env:
          CONTAINER_IMAGE_NAME: ${{ secrets.CONTAINER_IMAGE_NAME }}
          DOCKER_REGISTRY_URL: ${{ secrets.DOCKER_REGISTRY_URL }}
        run: docker push $DOCKER_REGISTRY_URL/$CONTAINER_IMAGE_NAME:latest
1 Like