# Cannot access Nessus when using bind mount in docker compose!

**URL:** <https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164>\
**Category:** General\
**Tags:** docker-compose, volumes\
**Created:** [October 4, 2024, 3:56am UTC](https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164 "2024-10-04T03:56:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![thanhlamuit2020](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/thanhlamuit2020/32/52311_2.png) [@thanhlamuit2020](https://forums.docker.com/u/thanhlamuit2020)\
**Post date:** [October 4, 2024, 3:56am UTC](https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164/1 "2024-10-04T03:56:47Z")

</div>

Host: Oracle Linux 9.4  
Docker compose version: 2.29.7

I am using docker compose to create an nessus container. If I use volume mount, the service run susscessfully. But when I use bind mount to my host folder, the service cannot run because missing plugin file.

This is my docker-compose file content:

services:  
nessus\_service:  
image: tenable/nessus:10.8.3-oracle  
restart: always  
container\_name: nessus\_container  
ports:  
- 3002:8834  
volumes:  
- /home/my\_mount\_folder\_nessus:/opt/nessus/var/nessus/

---

<div class="post-metadata">

**Author:** ![deanayalon](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/deanayalon/32/49113_2.png) [@deanayalon](https://forums.docker.com/u/deanayalon)\
**Post date:** [October 4, 2024, 5:01am UTC](https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164/2 "2024-10-04T05:01:37Z")

</div>

An empty volume initializes with the contents of the image at the path it’s mounted. A bind mount does not change its contents, what’s in your computer overrides the image contents. Do you have the required things in the mount path?

---

<div class="post-metadata">

**Author:** ![meyay](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/meyay/32/34000_2.png) [@meyay](https://forums.docker.com/u/meyay)\
**Post date:** [October 4, 2024, 1:40pm UTC](https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164/3 "2024-10-04T13:40:41Z")

</div>

This image looks like fun 😃

> Note: Tenable Nessus does not support storage volumes. Therefore, if you deploy a new Tenable Nessus image, you will lose your data and need to reconfigure Tenable Nessus. However, while deploying the new image, you can configure any initial user and linking information with environment variables, as described in step two of the following procedure.

Source: [Deploy Tenable Nessus as a Docker Image (Tenable Nessus 10.8)](https://docs.tenable.com/nessus/Content/DeployNessusDocker.htm)

---

<div class="post-metadata">

**Author:** ![deanayalon](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/deanayalon/32/49113_2.png) [@deanayalon](https://forums.docker.com/u/deanayalon)\
**Post date:** [October 4, 2024, 1:53pm UTC](https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164/4 "2024-10-04T13:53:04Z")

</div>

That is interesting, any idea why they’d do that?

---

<div class="post-metadata">

**Author:** ![meyay](https://sea3.discourse-cdn.com/docker/user_avatar/forums.docker.com/meyay/32/34000_2.png) [@meyay](https://forums.docker.com/u/meyay)\
**Post date:** [October 4, 2024, 2:56pm UTC](https://forums.docker.com/t/cannot-access-nessus-when-using-bind-mount-in-docker-compose/144164/5 "2024-10-04T14:56:49Z")

</div>

I can only make an educated guess: It appears that parts of the application code and persistent state are stored in the same folder, and maybe separating the state from the application code would be too much of a hustle…

In short: I have not the faintest idea 😃