Error: could not authenticate: user githubactions not entitled to use Docker Scout
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 141
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
i have this error if i use Login to a registry to pull private images (non Docker Hub. I add here registry-user and registry-password Service principle, Access key and user name, PAT and name of PAT. It always do not work.Byt if I use dockerhub user and dockerhub password it is work. What is problem? I tried use also login-action witt ACR and I had login succeeded but docker scout always failed. My action
name: Build and Scan Docker Image
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v2
- name: Login to ACR
uses: docker/login-action@v3
with:
registry: test.azurecr.io
username: test
password: test123
- name: Build and Push Bckend
shell: bash
run: |
docker build -t my-node-app .
- name: Docker Scout
id: docker-scout
if: ${{ github.event_name != 'pull_request_target' }}
uses: docker/scout-action@v1.10.0
with:
command: cves
image: my-node-app
only-severities: low
exit-code: true how to fix?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides a GitHub Actions workflow using docker/login-action@v3 and docker/scout-action@v1.10.0 against test.azurecr.io; begin by reproducing that workflow with the reported registry credentials and reviewing the Scout action's authentication behavior. Done means identifying why the non-Docker Hub login is rejected and recording or implementing a verified fix, with any relevant tests or documentation updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, docker, github-actions, javascript
- Domain
- ci-cd, cloud, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100