[BUG] ERROR, unable to validate 'conf.yml'

[0n1cOn3]

Environment

Self-Hosted (Docker)

System

Fedora Server 37

Version

V-2.1.1

Describe the problem

1. Clone the dashy repos to a directory of my choice (/home/user/Docker-Tests or /docker)
2. Adjustment path of the configuration file
3. Start the container

Instant Error as in the description already mentioned
Does not matter if with root or non-root user account.
When entering the website, the console also spits out an error (It's obvious why ;) )

Error: EACCES: permission denied, stat '/app/public/conf.yml'

Additional info

Firefox Dev Utilities Output:

Deprecation warning: The simple-icons entrypoint will be removed in the next major. Please switch to using import * as icons from "simple-icons/icons" if you need an object with all the icons. index.js:1:8
XHRGEThttp://10.1.200.240/conf.yml
[HTTP/1.1 500 Internal Server Error 5ms]

Uncaught (in promise)
Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }
asyncToGenerator.js:6:4
XHRGEThttp://10.1.200.240/conf.yml
[HTTP/1.1 500 Internal Server Error 5ms]

Object { message: "Request failed with status code 500", name: "AxiosError", code: "ERR_BAD_RESPONSE", config: {…}, request: XMLHttpRequest, response: {…}, stack: "" }

Please tick the boxes

• You have explained the issue clearly, and included all relevant info
• You are using a supported version of Dashy
• You've checked that this issue hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[jeangjenq]

Still relevant, pretty much went through the same steps in this issue today and experiencing the exact same thing.

[dashy] | yarn run v1.22.15
[dashy] | $ node server
[dashy] | 
[dashy] | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[dashy] |  Error, unable to validate 'conf.yml' 
[dashy] | ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[dashy] | 
[dashy] | ⚠️ Permission denied 
[dashy] | 
[dashy] | SSL Not Enabled: Public key not present
[dashy] | 
[dashy] | 
[dashy] |  ██████╗  █████╗ ███████╗██╗  ██╗██╗   ██╗
[dashy] |  ██╔══██╗██╔══██╗██╔════╝██║  ██║╚██╗ ██╔╝
[dashy] |  ██║  ██║███████║███████╗███████║ ╚████╔╝
[dashy] |  ██║  ██║██╔══██║╚════██║██╔══██║  ╚██╔╝
[dashy] |  ██████╔╝██║  ██║███████║██║  ██║   ██║
[dashy] |  ╚═════╝ ╚═╝  ╚═╝╚══════╝╚═╝  ╚═╝   ╚═╝
[dashy] | 
[dashy] | *******************************************************************************************
[dashy] | Welcome to Dashy! 🚀
[dashy] | Your new dashboard is now up and running with Docker
[dashy] | *******************************************************************************************
[dashy] | 
[dashy] | 
[dashy] | Using Dashy V-2.1.1. Update Check Complete
[dashy] | ✅ Dashy is Up-to-Date
[dashy] | 
Error: EACCES: permission denied, stat '/app/public/conf.yml'
Error: EACCES: permission denied, stat '/app/public/conf.yml'

[jeangjenq]

@0n1cOn3
I made some progress today. I tested this on both Fedora Workstation and Fedora Silverblue 38.
If I use the docker and docker-compose from fedora software repository,
sudo dnf install docker docker-compose in Workstation.
rpm-ostree install docker docker-compose in Silverblue.
This issue occurs.

But if you follow the official docker engine installation instructions here.
Dashy starts up without issue.
Workstation:

sudo dnf -y install dnf-plugins-core
sudo dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo
sudo dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Silverblue:

cd /etc/yum.repos.d/
wget https://download.docker.com/linux/fedora/docker-ce.repo
rpm-ostree install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

[Joker214kk]

yarn run v1.22.15
$ node server

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Error, unable to validate 'conf.yml'
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⚠️ Config file could not be found at ./public/conf.yml

SSL Not Enabled: Public key not present

██████╗ █████╗ ███████╗██╗ ██╗██╗ ██╗
██╔══██╗██╔══██╗██╔════╝██║ ██║╚██╗ ██╔╝
██║ ██║███████║███████╗███████║ ╚████╔╝
██║ ██║██╔══██║╚════██║██╔══██║ ╚██╔╝
██████╔╝██║ ██║███████║██║ ██║ ██║
╚═════╝ ╚═╝ ╚═╝╚══════╝╚═╝ ╚═╝ ╚═╝

---

Welcome to Dashy! 🚀
Your new dashboard is now up and running with Docker

---

Using Dashy V-2.1.1. Update Check Complete
✅ Dashy is Up-to-Date

I have the same identical issue on Debian 11, where I executed it on docker-compose

dashy:
image: ghcr.io/lissy93/dashy:latest
container_name: Dashy
volumes:
- /opt/dashy/public:/app/public
- /opt/dashy/item-icons:/app/item-icons
ports:
- 4000:80
environment:
- UID=1000
- GID=1000
restart: always
healthcheck:
test: ['CMD', 'node', '/app/services/healthcheck']
interval: 1m30s
timeout: 10s
retries: 3
start_period: 40s

[elendil7]

Getting the same issue here, with docker-compose

  # Dashy Dashboard
  dashy:
    # To build from source, replace 'image: lissy93/dashy' with 'build: .'
    # build: .
    image: lissy93/dashy:latest
    container_name: dashy
    build:
      context: ./services/dashy
      dockerfile: Dockerfile.yml
    # Pass in your config file below, by specifying the path on your host machine
    volumes:
      - ./services/dashy/public:/app/public
    # ports:
    #   - 4000:80
    # Set any environmental variables
    environment:
      - NODE_ENV=production
    # Specify your user ID and group ID. You can find this by running `id -u` and `id -g`
    #  - UID=1000
    #  - GID=1000
    # Specify restart policy
    restart: unless-stopped
    depends_on:
      - nginx

[CrazyWolf13]

2. Adjustment path of the configuration file

Hi
This issue seems to containe mutiple different problems. Please create a new issue if you problem still persists, otherwise this ticket will get very quickly messy.

Issue 1, by @0n1cOn3:
If I understand Adjustment path of the configuration file corretly, you mean changing the path of conf.yml?

That is not supported, and will as you mentioned result in an error, then this would be a duplicate, see here -> #1322

Issue 2, by @jeangjenq :
Thanks for sharing! Good to know 👍

Issue 3, @elendil7 and @Joker214kk
You are mounting /app/public which is not really supported and results in a lot of problems, please mount the conf directly like described in the installation guide: https://dashy.to/docs/quick-start#2-installation
If that does give the same error, you may have to rebuild the container and mounting the conf directly instead of /app/public

Quick Start | Dashy

Welcome to Dashy! So glad you're here 😊 In a couple of minutes, you'll have your new dashboard up and running 🚀

[0n1cOn3]

Issue 1, by @0n1cOn3: If I understand Adjustment path of the configuration file corretly, you mean changing the path of conf.yml?

Yes, outside the container. It does not affect the location of the file in the container but on the host.
What confuses me is that this cannot be changed without Dashy's container spitting out this error.
It is a mystery to me why this happens, because it works fine with other containers.

[CrazyWolf13]

Issue 1, by @0n1cOn3: If I understand Adjustment path of the configuration file corretly, you mean changing the path of conf.yml?

Yes, outside the container. It does not affect the location of the file in the container but on the host. What confuses me is that this cannot be changed without Dashy's container spitting out this error. It is a mystery to me why this happens, because it works fine with other containers.

If this error appears, does dashy load normal or are there any errors in the UI?

Can you do a rebuild and show the output here? either through GUI or through yarn build-and-start inside the container

[CrazyWolf13]

@0n1cOn3

Could you descibe this in some steps? I can't really recreate this issue.

If I understand you correctly, you are changing the bind mount to another place on the host and expect the docker container to copy the file from dashy container to the new location?

This will not work as bind mounts are only one directional.

Also if the error appears, can you look into the container and see if the config file is there?
You can check this with sudo docker exec -it {container-name} /bin/sh

cd public
ls
cat conf.yml

Post the output of cat and ls command here please.

[liss-bot]

Hello! Looks like additional info is required for this issue to be addressed. Don't forget to provide this within the next few days to keep your ticket open.

[liss-bot]

Issue closed due to no response from user.