[PR #91] Fix: mount configs directory into worker container #114

New issue

Open

opened 2026-02-27 07:20:28 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 07:20:28 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/KeygraphHQ/shannon/pull/91
Author: @mattiasgeniar
Created: 2/8/2026
Status: 🔄 Open

Base: main ← Head: fix/mount-configs-volume

📝 Commits (1)

a86d63d Mount configs directory into worker container

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 docker-compose.yml (+1 -0)

📄 Description

Summary

The README documents CONFIG=./configs/my-config.yaml as a usage example, but this fails at runtime with "Configuration file not found" because the configs/ directory was never mounted into the worker container
Add ./configs:/app/configs:ro volume mount to the worker service, consistent with how ./prompts is already mounted

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/KeygraphHQ/shannon/pull/91 **Author:** [@mattiasgeniar](https://github.com/mattiasgeniar) **Created:** 2/8/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/mount-configs-volume` --- ### 📝 Commits (1) - [`a86d63d`](https://github.com/KeygraphHQ/shannon/commit/a86d63d0ff8e6d0af355fd828c0efef782a4bae4) Mount configs directory into worker container ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docker-compose.yml` (+1 -0) </details> ### 📄 Description ## Summary - The README documents `CONFIG=./configs/my-config.yaml` as a usage example, but this fails at runtime with "Configuration file not found" because the `configs/` directory was never mounted into the worker container - Add `./configs:/app/configs:ro` volume mount to the worker service, consistent with how `./prompts` is already mounted --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>