Containers for running the Greenbone Vulnerability Manager. Run as a single container with all services or separate single applications containers via docker-compose.
GNU Affero General Public License v3.0
366
stars
102
forks
source link
[BUG] Issues with latest container not starting? #273
Has their been a new container released in the past 48 hours? On one of my three watcher boxes which is updated each Friday I am unable to run the docker image. However my two other boxes which were patched earlier this week are working as they should. I don't want to stop them to test if machine specific or not unless I have to incase there is an issue with the container.
This morning I pactched my OpenSuse Leap 15.5 server as normal and rebooted. I ran a system rpune -a on the containers and checked with docker ps --all as normal. When i Use my docker run command:
nothing seems to happen other than sitting on a > cursor. All other docker commands and functions seem to work and I have restarted the server and the docker service with no change in behaviour. I am not sure if a docker issue or an image issue as it is not pulling it down or attempting to.
Has their been a new container released in the past 48 hours? On one of my three watcher boxes which is updated each Friday I am unable to run the docker image. However my two other boxes which were patched earlier this week are working as they should. I don't want to stop them to test if machine specific or not unless I have to incase there is an issue with the container.
This morning I pactched my OpenSuse Leap 15.5 server as normal and rebooted. I ran a system rpune -a on the containers and checked with docker ps --all as normal. When i Use my docker run command:
docker run --detach --publish 8443:9392 -e PASSWORD="REDACTED" --volume openvas:/data -e HTTPS=true --name openvas immauss/openvas:latest
nothing seems to happen other than sitting on a > cursor. All other docker commands and functions seem to work and I have restarted the server and the docker service with no change in behaviour. I am not sure if a docker issue or an image issue as it is not pulling it down or attempting to.