You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The documentation says: "The Docker image has been updated to run as a non-root user." However, lines 30-32 of the docker-compose.yml file say:
volumes:
- .env:/opt/scancodeio/.env
- /etc/scancodeio/:/etc/scancodeio/
[etc]
If this directory has not been created by the root user, then this mapping fails and the web and worker images fail to be created/load.
System configuration
This is the current version, running using podman/podman-compose on Debian 13/Trixie.
Error:
Error: "scancodeio_web_1" is not a valid container, cannot be used as a dependency: no container with name or ID "scancodeio_web_1" found: no such container
Error: "scancodeio_web_1" is not a valid container, cannot be used as a dependency: no container with name or ID "scancodeio_web_1" found: no such container
[web] | Error: no container with name or ID "scancodeio_web_1" found: no such container
[nginx] | Error: no container with name or ID "scancodeio_nginx_1" found: no such container
[worker] | Error: no container with name or ID "scancodeio_worker_1" found: no such container
Expected behavior
Should start all containers and go up.
The text was updated successfully, but these errors were encountered:
Hey @VanL , Let me look into it. I've cloned the repository on my system let me know any specific files should I look into? though I'm understanding how container is build. Thank you!
Describe the bug
The documentation says: "The Docker image has been updated to run as a non-root user." However, lines 30-32 of the docker-compose.yml file say:
volumes:
- .env:/opt/scancodeio/.env
- /etc/scancodeio/:/etc/scancodeio/
[etc]
If this directory has not been created by the root user, then this mapping fails and the web and worker images fail to be created/load.
System configuration
To Reproduce
Steps to reproduce the behavior:
Error: "scancodeio_web_1" is not a valid container, cannot be used as a dependency: no container with name or ID "scancodeio_web_1" found: no such container
Error: "scancodeio_web_1" is not a valid container, cannot be used as a dependency: no container with name or ID "scancodeio_web_1" found: no such container
[web] | Error: no container with name or ID "scancodeio_web_1" found: no such container
[nginx] | Error: no container with name or ID "scancodeio_nginx_1" found: no such container
[worker] | Error: no container with name or ID "scancodeio_worker_1" found: no such container
Expected behavior
Should start all containers and go up.
The text was updated successfully, but these errors were encountered: