search

StamusNetworks / Amsterdam

Docker based Suricata, Elasticsearch, Logstash, Kibana, Scirius aka SELKS
GNU General Public License v3.0
183 stars 42 forks source link

Guidance - suricata.yaml\\\" caused \\\"not a directory\\\"\"" #52

Open monokal opened 6 years ago

monokal commented 6 years ago

Hey,

I'm working on some changes to the repo in order to open a PR, namely getting Amsterdam itself to run in a container and therefore requiring no littering of the underlying host. I'm very close, however, Amsterdam is having an issue deploying the suricata service in particular as per the below error:

Starting data_suricata_1 ... error

ERROR: for data_suricata_1  Cannot start service suricata: oci runtime error: container_linux.go:262: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:57: mounting \\\"/opt/Amsterdam/data/config/suricata/suricata.yaml\\\" to rootfs \\\"/var/lib/docker/overlay2/c63115e1ff44923ae65ece97b40a3b8bcec448e1c7c42b8d0c5672d05ed8d58c/merged\\\" at \\\"/var/lib/docker/overlay2/c63115e1ff44923ae65ece97b40a3b8bcec448e1c7c42b8d0c5672d05ed8d58c/merged/etc/suricata/suricata.yaml\\\" caused \\\"not a directory\\\"\""

Other containers start up just fine. Any ideas?

For reference, my repo is https://github.com/monokal/Amsterdam.git and the Amsterdam container can be built and run like so:

./dbuild.sh build && ./dbuild.sh test
regit commented 6 years ago

Looks like mounting a file is not working in this case. It looks like it appaears in some cases: https://forums.docker.com/t/unable-to-mount-directories-files-from-docker-compose-oci-runtime-error-not-a-directory/10808/5 What OS and docker version are you using ?