Bind-mount data dir and proxy support

[davidkarlsen]

Do you support keeping the database-state as a bindmount/volume-mount (should maybe be signaled as a VOLUME in the Dockerfile?)
Also do you support reading proxy-settings for retrieving the updates?

[stefanneuhaus]

Currently neither of the two is supported, but I think they are useful features which I would like to add. Especially the proxy is probably a must-have in many environments.

I do not yet know when I find the time to implement these. But they are definitely on my to do list. And of course pull requests are welcome.

Regarding the proxy config: If you do not mind building the Docker image on your own, you can just drop the proxy config into the dependencyCheck configuration block and build the Docker image. This is the configuration for the regular CVE DB update job.

[stefanneuhaus]

@davidkarlsen You can use the mount point /var/lib/mysql for the database data. It has always been in place (as the image extends from the mysql image) but I had not yet been aware of it or tested it.

I will update the documentation soon. I will also add the VOLUME instruction in the Dockerfile as you proposed.

[davidkarlsen]

@stefanneuhaus Actually I think it is already inherited from the parent image (if it declares a VOLUME): moby/moby#3465

[odin568]

It would be cool to just pass in HTTP_PROXY and HTTPS_PROXY variable from the host system. You see any chance to integrate that generically that it works with and without?

[nauni77]

@davidkarlsen You can use the mount point /var/lib/mysql for the database data. It has always been in place (as the image extends from the mysql image) but I had not yet been aware of it or tested it.

I will update the documentation soon. I will also add the VOLUME instruction in the Dockerfile as you proposed.

Hello, this is not possible OOTB. Because of some reasons, most important is the password for updating the database. This changes from container release to next container release.

I changed the thinks to handle this and created a pull request:
"add multi arch build for amd64 and arm64 #21"

This also fix this topic. But Stefan need to check and aprove.

[nauni77]

It would be cool to just pass in HTTP_PROXY and HTTPS_PROXY variable from the host system. You see any chance to integrate that generically that it works with and without?

This is not possible to make this happen at container. But you can take care for this during start ...

docker run --rm --name owasp-db -p 3306:3306 \
    -v owasp-db:/var/lib/mysql \
    -e NVD_API_KEY=<yourKey> \
    -e HTTP_PROXY=$HTTP_PROXY \
    -e HTTPS_PROXY=$HTTPS_PROXY \
    -d stefanneuhaus/dependencycheck-central-mysql

The HTTP_PROXY environment variable at container will be set to the value of $HTTP_PROXY from host system. I didn't check this explicitly, but thats the way it works usually.

[nauni77]

I changed the thinks to handle this and created a pull request: "add multi arch build for amd64 and arm64 #21"

Nobody take care for the pull request and I need to update my fork of this project. So the Pull-Request is removed. If someone want to enhance

• storage
• pull frequency
• ...

you can tell me and I will create a new pull request.