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
{{ message }}
This repository has been archived by the owner on Nov 4, 2022. It is now read-only.
When I set the crond command to debug crond -s /var/spool/cron/crontabs -f -d -l 8 in src/docker/conf/supervisord.conf the logs show that the mirror script is run twice: once for user root and once for user mirror. Is this behaviour intended?
I can confirm that the user mirror is not necessary for the setup. I build the image without the user mirror and the cron is running only for user root. The files are served the same way as before. I also deployed the helm chart to k8s and can confirm that it works, too. I can target the k8s mirror when using dependency-check without any issues.
When I set the crond command to debug
crond -s /var/spool/cron/crontabs -f -d -l 8
insrc/docker/conf/supervisord.conf
the logs show that the mirror script is run twice: once for userroot
and once for usermirror
. Is this behaviour intended?I can confirm that the user
mirror
is not necessary for the setup. I build the image without the usermirror
and the cron is running only for userroot
. The files are served the same way as before. I also deployed the helm chart to k8s and can confirm that it works, too. I can target the k8s mirror when usingdependency-check
without any issues.From the Dockerfile (line 24-33):
From
src/docker/conf/supervisord.conf
(line 17-23):The text was updated successfully, but these errors were encountered: