Releases: opencve/opencve-docker
Releases · opencve/opencve-docker
v1.5.0
Updates
Bump to 1.5.0 OpenCVE version. Please read carefully the change log of the 1.5.0 OpenCVE release.
This version brings the support of the new NVD endpoints.
How to upgrade
# Check if there is no updates ongoing on the celery_worker:
$ docker logs celery_worker
# If or when there is no update ongoing:
$ docker stop celery_beat celery_worker webserver
# Update opencve-docker repository:
$ git pull --prune
# Check that you are on the correct version:
$ grep OPENCVE_VERSION .env
OPENCVE_VERSION=1.5.0
# Build the new docker images:
$ docker-compose build
# Start the webserser:
$ docker-compose up -d webserver
# Ensure you have the version 1.5.0:
$ docker exec -it webserver opencve --version
opencve, version 1.5.0
# Backup your database and run the upgrade-db command to update the database schema:
$ docker exec -it webserver opencve upgrade-db
# Run the NVD migration, it takes some time to iterate on all the NVD indexes:
$ docker exec -it webserver opencve migrate-nvd
# When the migration is done, you are good to go, start the celery_worker & the beat:
$ docker-compose up -d celery_worker celery_beat
v1.4.1
v1.4.0
Updates
Bump to 1.4.0 OpenCVE version. Please read the change log of the 1.4.0 OpenCVE release.
Added
- Fix typo in PostgreSQL data path
- Upgrade python version from 3.7 to 3.8
- Allow image build from specific repository/branch
Configuration
The following parameters have been added in the opencve.cfg configuration file, please update your configuration file if needed:
- celery_lock_url
- include_analytics
- reports_cleanup_days
- smtp_use_ssl
Please update opencve.cfg if you need to change the default values.
How to upgrade
# Check if there is no updates ongoing on the celery_worker:
$ docker logs celery_worker
# If or when there is no update ongoing:
$ docker stop celery_beat celery_worker webserver
# Update opencve-docker repository:
$ git pull --prune
# Update your opencve.cfg file with the changes if needed:
$ vi conf/opencve.cfg
# Check that you are on the correct version:
$ grep OPENCVE_VERSION .env
OPENCVE_VERSION=1.4.0
# Build the new docker images:
$ docker-compose build
# Start the webserver & celery_worker:
$ docker-compose up -d webserver celery_worker
# Upgrade the database schema:
$ docker exec -it webserver opencve upgrade-db
# Now you are good to go, you can start the beat:
$ docker-compose up -d celery_beat
v1.3.0
Updates
Bump to 1.3.0 OpenCVE version.
Added
- feat: Adding support for proxy to work in a proxy environment.
How to upgrade
# Check if there is no updates ongoing on the celery_worker:
$ docker logs celery_worker
# If or when there is no update ongoing:
$ docker stop celery_beat celery_worker webserver
# Update opencve-docker repository:
$ git pull --prune
# Update your opencve.cfg file with the changes
$ vi conf/opencve.cfg
# Check that you are on the correct version:
$ grep OPENCVE_VERSION .env
OPENCVE_VERSION=1.3.0
# Build the new docker images:
$ docker-compose build
# Start the webserver & celery_worker:
$ docker-compose up -d webserver celery_worker
# Upgrade the database schema:
$ docker exec -it webserver opencve upgrade-db
# Now you are good to go, you can start the beat:
$ docker-compose up -d celery_beat
v1.2.3
v1.2.2
v1.2.1
v1.2.0
Updates
Bump to 1.2.0 OpenCVE version.
How to upgrade
# Check if there is no updates ongoing on the celery_worker:
$ docker logs celery_worker
# If or when there is no update ongoing:
$ docker stop celery_beat celery_worker webserver
# Update opencve-docker repository:
$ git pull --prune
# Update your opencve.cfg file with the changes
$ vi conf/opencve.cfg
# Check that you are on the correct version:
$ grep OPENCVE_VERSION .env
OPENCVE_VERSION=1.2.0
# Build the new docker images:
$ docker-compose build
# Start the webserver & celery_worker:
$ docker-compose up -d webserver celery_worker
# Upgrade the database schema:
$ docker exec -it webserver opencve upgrade-db
INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO [alembic.runtime.migration] Will assume transactional DDL.
INFO [alembic.runtime.migration] Running upgrade f81abceece3d -> 33cd640e1112, Add indexes on cves.summary and cve.cve_id
INFO [alembic.runtime.migration] Running upgrade 33cd640e1112 -> 4195eeb432e9, Add tags tables
# Now you are good to go, you can start the beat:
$ docker-compose up -d celery_beat