Docker problem with Diode Server

[AltairWorke]

Diode version

new install

Deployment type

docker compose

Deployment type version

27.5.1

Diode SDK type

diode-sdk-python

Diode SDK version

unknown

Diode NetBox Plugin version

v1.2

NetBox version

v4.3.2

Steps to reproduce

mkdir -p /opt/diode
cd /opt/diode
curl -sSfLo quickstart.sh https://raw.githubusercontent.com/netboxlabs/diode/release/diode-server/docker/scripts/quickstart.sh
chmod +x quickstart.sh
./quickstart.sh https://mynetbox.domain.local
docker compose up -d

Expected behavior

diode server docker container to open

Observed behavior

Whether using docker compose up -d OR docker compose -f /opt/diode/docker-compose.yaml up -d

Get the following: open /opt/diode/docker-compose.yaml: no such file or directory

Running as root. yaml file can be opened and edited in nano

[akenawell85x]

to add to this, having same issue and all the same info as OP. If i list the directory there is a docker-compose.yml file there but i still get the no such file or directory error. I get the same error trying to cat the existing file, and if i try to open/edit the file with nano it opens as a new blank file, as if there is no current file in that directory. the current file in the directory has -r-rw-r--r-- permissions if that matters

[AltairWorke]

to add to this, having same issue and all the same info as OP. If i list the directory there is a docker-compose.yml file there but i still get the no such file or directory error. I get the same error trying to cat the existing file, and if i try to open/edit the file with nano it opens as a new blank file, as if there is no current file in that directory. the current file in the directory has -r-rw-r--r-- permissions if that matters

Not to take away from your issue, they may be, and likely are still related... but I have NO issues reading, opening, or changing the yaml file in my installation.

[OliElli]

It's the file extension: .yml vs .yaml

[AltairWorke]

It's the file extension: .yml vs .yaml

Very first thing I tried. However, specifying the docker file with the -f parameter ought to have overcome that anyway.

To be noted: The yaml file is the exact file downloaded from the NetBox Labs git based on the installation instructions from said same.