All geek questions in one place

Wercker deployment returns 404 for push-push

First time with Wercker, and I use internal/docker-push . When I run the deployment step, I get a 404 error from the dock hub.

 ERROR Error interacting with this repository: wluce/statler-waldorf-corp-team-service PUT https://registry.hub.docker.com/v1/repositories/wluce/statler-waldorf-corp-team-service/ returned 404

This is not the first time I have run this step, and it worked before. Image exists here .

I can’t understand what could have changed.

Here is the wercker.yml file that I use to build and deploy.

 box: microsoft/dotnet:2.0.0-sdk-2.0.2 no-response-timeout: 10 build: steps: - script: name: restore cwd: src/StatlerWaldorfCorp.TeamService code: dotnet restore - script: name: build cwd: src/StatlerWaldorfCorp.TeamService code: dotnet build - script: name: test-restore cwd: test/StatlerWaldorfCorp.TeamService.Tests code: dotnet restore - script: name: test-build cwd: test/StatlerWaldorfCorp.TeamService.Tests code: dotnet build - script: name: test-run cwd: test/StatlerWaldorfCorp.TeamService.Tests code: dotnet test - script: name: integration-test-restore cwd: test/StatlerWaldorfCorp.TeamService.Tests.Integration code: dotnet restore - script: name: integration-test-build cwd: test/StatlerWaldorfCorp.TeamService.Tests.Integration code: dotnet build - script: name: integration-test-run cwd: test/StatlerWaldorfCorp.TeamService.Tests.Integration code: dotnet test - script: name: publish cwd: src/StatlerWaldorfCorp.TeamService code: dotnet publish -o publish - script: name: copy binary cwd: src/StatlerWaldorfCorp.TeamService code: cp -r . $WERCKER_OUTPUT_DIR/app deploy: box: microsoft/aspnetcore:2.0.0 steps: - internal/docker-push: cwd: $WERCKER_OUTPUT_DIR/app username: $DOCKER_USERNAME password: $DOCKER_PASSWORD repository: wluce/statler-waldorf-corp-team-service registry: https://registry.hub.docker.com entrypoint: "/pipeline/source/app/docker_entrypoint.sh"
+5
source share
2 answers

As discussed on the Wercker slack channel and suggested by @cggaldes, the solution is to set the full registry address in the step definition, for example:

 - internal/docker-push: registry: https://registry.hub.docker.com/v2 <-- This repository: org/repo username: $DOCKER_USER password: $DOCKER_PASS ...

Apparently internal/docker-push uses v1 by default, which has recently changed / broken.

+3
source

In the internal / docker step, just add the registry with v2 added so that wercker uses the v2 registry api like this

  repository: gapostolov/course-repo registry: https://registry.hub.docker.com/v2
0
source

Source: https://habr.com/ru/post/1273340/

More articles:


All Articles