@NAS Newbie
I've actually made it stupidly easy now I think... (NB Think).
My compose is:
Code:
version: "3"
services:
nessus:
container_name: nessus
image: akirainblack/nessus:latest
volumes:
- ${SSD}nessus/config:/config
- ${SSD}nessus/update:/update
- PUID=${USERID}
- PGID=${USERGROUP}
ports:
- 8834:8834
networks:
- synology
restart: always
networks:
synology:
external: true
So
Ok, It's based on Centos 8 (of note for the update section).
Not sure why but it's not showing in my registry in DSM yet but it does exist, once it shows you'd be able to create it as with any other container:
Code:
https://hub.docker.com/r/akirainblack/nessus
Though running:
docker pull akirainblack/nessus:latest
from an ssh into the NAS finds and downloads it so you could just do that and then find it in your images in the UI.
You have to map a folder to /config - it'll extract the nessus rpm to there and it's used so that your license and settings remain between reboots.
It already has the current rpm ready in the image to extract (Nessus-8.13.1-es8.x86_64.rpm at time of writing).
It's optional to map a folder to /update (on boot it will look for an rpm in that folder and attempt to extract it) It has no logic so will just extract and overwrite.
Internal port is 8834 which will need to be mapped.
If you can't wait (see above for an easier way to get the image):
ssh into your nas, navigate to your docker folder:
mkdir nessus
cd nessus
mkdir /config
mkdir /update
modify the nessus.yml so that ${SSD}/nessus/config and ${SSD}/nessus/update point to these new folders, save it to your NAS (in my case I save it to /volume2/docker/compose) and then from the directory you saved it to run:
sudo docker-compose -f nessus.yml up -d
Obviously change the network name to the one you use in your docker environment first.
Can attach the Dockerfile and setup.sh it runs if people want to see it (they're not very pretty as I'm very new to creating containers from scratch).
Basically on boot it extracts it's internal nessus.rpm (unless one is found in the update folder) extracts that , creates a symlink to where it would normally be installed, and then runs nessus-service.
The initial WebUI is up pretty quickly it's just the plugins that take time to load. It'll then run you through the initial config.