deepfence / ThreatMapper

Open Source Cloud Native Application Protection Platform (CNAPP)
https://deepfence.io
Apache License 2.0
4.85k stars 584 forks source link

GitLab Registry Scan not working #535

Open hubby2004 opened 2 years ago

hubby2004 commented 2 years ago

Describe the bug When adding a GitLab registry, it does not detect the published containers images.

To Reproduce Steps to reproduce the behavior:

  1. Go to 'Registries'
  2. Click on 'GitLab'
  3. Click on '+Add Registry'
  4. Enter the registry's information a. Registry Name: GitLab b. GitLab Registry Server URL: https://gitlab.domain.local c. GitLab Registry URL: gitlab.domain.local d. Token: xxxxxxxxxxxxxxxxxx
  5. Click 'Save Credentials'
  6. The page shows a new entry for the GitLab registry but no images detected

Expected behavior After adding the GitLab registry, it should show the Total Images being more than 0.

Screenshots image

Components/Services affected

Additional context Environment Information: Component Version
Deepfence 1.4.0
Docker host OS Ubuntu 20.04.4 LTS
Docker 20.10.12
GitLab 15.0.5-ee
mukuldeepfence commented 2 years ago

@hubby2004 is adding Gitlab container registry to the console working now ?

hubby2004 commented 2 years ago

@mukuldeepfence few containers showed up but they are gone now and displaying 0

ibreakthecloud commented 2 years ago

@mukuldeepfence any update on this?

saurabh2253 commented 2 years ago

https://github.com/deepfence/enterprise-roadmap/issues/1591#issuecomment-1283813346

saurabh2253 commented 2 years ago

@hubby2004 Please ensure you enter credentials in following sample format: Registry Name: GcrTest Gitlab Server URL: https://gitlab.com Gitlab Registry URL: registry.gitlab.com/saurabh149/privatetest Gitlab Personal Access Token: xxxx Kindly let us know if it still doesn't work