Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Solution
GitHub Staff
Message 11 of 15

Re: Github Actions Docker login

This is a known issue that we're working to resolve.  GITHUB_TOKEN works for publishing most types of packages (eg, npm) but not yet for all.  This will work for all types of packages - including Docker - by the time GitHub Actions and GitHub Package Registry is out of beta.

Copilot Lvl 2
Message 12 of 15

Re: Github Actions Docker login

According to today's announcement, GitHub package registry will leave beta on 13 November. Does that mean this issue has been (or is close to being) resolved?
Pilot Lvl 1
Message 13 of 15

Re: Github Actions Docker login

I've had success with the following step:

 

    - name: Push
      run: |
        docker login docker.pkg.github.com --username RepoOwner --password "${GITHUB_PACKAGE_REGISTRY_TOKEN}"
        docker push docker.pkg.github.com/repoowner/repo_name/image_name:tag
      env:
        GITHUB_PACKAGE_REGISTRY_TOKEN: ${{ secrets.GITHUB_PACKAGE_REGISTRY_TOKEN }}

 

Note: The Docker image name is lowercase. The username for docker login may contain uppercase letters. Make sure to convert them to lowercase when building the image tag string. "RepoOwner" -> "repoowner". Same goes for the repository name.

 

Here's a full example: https://github.com/chrispat/actions-container-service/blob/master/.github/workflows/build-and-deploy...

Copilot Lvl 3
Message 14 of 15

Re: Github Actions Docker login

https://github.com/actions/docker repo is now a 404. Anyone know why?

Mission Specialist Lvl 1
Message 15 of 15

Re: Github Actions Docker login

It has been deprecated for some time and they finally removed it.  Docker cli commands can be run directly from all the base images now so it wasn't needed anymore.