Welcome to scancode.io Discussions!

[tdruez]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you'll use this space to:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others with an open-minded attitude. Remember that this is a community we build together 💪.

To get started, comment below with an introduction of yourself and tell us why you joined this community.

[Khan-Tzar]

Hello,
Could you consider CPU, Memory container limitations into docker-compose.yml , please?
Something like this:

web:
    build: .
    command: sh -c "
        ./manage.py migrate &&
        ./manage.py collectstatic --no-input --verbosity 0 --clear &&
        gunicorn scancodeio.wsgi:application --bind :8000 --timeout 600 --workers 8"
    env_file:
      - docker.env
    expose:
      - 8000
    volumes:
      - /etc/scancodeio/:/etc/scancodeio/
      - workspace:/var/scancodeio/workspace/
      - static:/var/scancodeio/static/
    depends_on:
      - db
    restart: always
    deploy:
        resources:
            limits:
                cpus: 2
                memory: 4096m
            reservations:
                memory: 512m

[tdruez]

Hi @Khan-Tzar, could you provide more context about your issues and the benefits of forcing those limitations?

[19csa55]

Hello,

I'm a newbie, and as I've understood, while starting a new project, the Docker URL provided points to Docker Hub and all the images uploaded there.

I was wondering if I could provide a URL for referring to an image in another private image repository, hosted in a private network, such as Harbor.

Harbor is private image repository that can be hosted and managed. Is it possible to use Scancode.io with that?

P.S. I think I've disturbed an ancient thread. Sorry in advance!

[pombredanne]

@19csa55 we prefer using public discussions rather than private messages unless this is a private matter and I doubt this is the cases here.
In short:

• we run skopeo to fetch container images
• to access private container registries we would need to provide authentication. One design is to store auth in some settings and/or envt. var. There may be other ways though that should be explored, like the standard docker auth JSON file.

Can you start by installing and playing with skopeo?

[19csa55]

Hello @pombredanne

Ah, well thanks for the quick response anyways!

Can you tell me more about storing auth settings? I have even tried to change the skopeo command being used in /scanpipes/pipes/fetch.py to add my creds and make it point to the Harbor registry that I'm using, but it seems that it causes an error in the run_command_safely() function where a subprocess is used.

[19csa55]

@pombredanne Hello.

I've gotten a bit of it working now, is it possible for you to guide me through any troubleshooting procedures while the docker image is running? It's difficult for me to look at the output of the subprocess commands.

[tdruez]

Support for private Docker registry added in #1098
See https://scancodeio.readthedocs.io/en/latest/faq.html#how-to-fetch-files-from-private-sources-and-protected-by-credentials and https://scancodeio.readthedocs.io/en/latest/application-settings.html#scancodeio-skopeo-credentials

@19csa55 could you give it a try and let me know it that approach works for you?

[19csa55]

Was told to look back into this and it now works, thanks for your help!