I want to use Repos scripts to use sops to decrypt my env files. This works as expected. But the decrypted files are not available to "Run Sync" and "Deploy Stack" Executions (as they seem to use the /repo-cache).
Is it intended that the scripts only edit the periphery copy and not the /repo-cache?
Example of an Error:
ERROR: Failed to read file contents from "/repo-cache/github.com/gitaccount-repo/main/latest/services/server/it-tools/compose.env"
TRACE:
1: No such file or directory (os error 2)
The file exists, but only under /data/repos/repo/services/server/it-tools/compose.env
My config
compose.yaml
services:mongo:image:mongo:8.0.15@sha256:d0d76261e7a19aee701e890a9e835ba369a12b8733e7d39cd89a923ed97f247clabels:komodo.skip:# Prevent Komodo from stopping with StopAllContainerscommand:--quiet --wiredTigerCacheSizeGB 0.25restart:unless-stoppedvolumes:- ${KOMODO_BASE_PATH}/mongo/data:/data/db- ${KOMODO_BASE_PATH}/mongo/config:/data/configdbenvironment:MONGO_INITDB_ROOT_USERNAME:${KOMODO_DB_USERNAME}MONGO_INITDB_ROOT_PASSWORD:${KOMODO_DB_PASSWORD}core:image:ghcr.io/moghtech/komodo-core:1.19.5@sha256:a1cceb4f971443b1e9f2a767788f663d0afb6244ee2135f7fe3fd1036af37adelabels:komodo.skip:# Prevent Komodo from stopping with StopAllContainersrestart:unless-stoppeddepends_on:- mongoports:- 9120:9120env_file:./compose.envenvironment:KOMODO_DATABASE_ADDRESS:mongo:27017KOMODO_DATABASE_USERNAME:${KOMODO_DB_USERNAME}KOMODO_DATABASE_PASSWORD:${KOMODO_DB_PASSWORD}volumes:- ${KOMODO_BASE_PATH}/backups:/backups- ${KOMODO_BASE_PATH}/repo-cache:/repo-cacheperiphery:image:ghcr.io/moghtech/komodo-periphery:1.19.5@sha256:bd79cf960ed054fe8e02384322303e462448679b1149dde48bbef151417255b1labels:komodo.skip:# Prevent Komodo from stopping with StopAllContainersrestart:unless-stoppedenv_file:./compose.envvolumes:- /var/run/docker.sock:/var/run/docker.sock- /proc:/proc- ${KOMODO_BASE_PATH}/data:${KOMODO_BASE_PATH}/data- ${KOMODO_BASE_PATH}/repos:${KOMODO_BASE_PATH}/repos
I was running into the same issue but I think I discovered the solution. In the new compose files it no longer lists the repo-cache as a volume to be mounted. I removed it from my set up and I no longer receive that error.
<!-- gh-comment-id:3423733627 -->
@jpod20 commented on GitHub (Oct 20, 2025):
I was running into the same issue but I think I discovered the solution. In the new compose files it no longer lists the repo-cache as a volume to be mounted. I removed it from my set up and I no longer receive that error.
https://github.com/moghtech/komodo/blob/main/compose/mongo.compose.yaml
I removed the repo cache from the volume mapping, but the behaviour is unchanged.
The Stack-UI reads the file from /repo-cache/github.com/gitaccount-repo/main/latest/services/server/it-tools/compose.env (core)
while the repo is executing the script on ${KOMODO_BASE_PATH}/data/repos/homelab (periphery)
<!-- gh-comment-id:3438920607 -->
@joecksma commented on GitHub (Oct 23, 2025):
I removed the repo cache from the volume mapping, but the behaviour is unchanged.
The Stack-UI reads the file from `/repo-cache/github.com/gitaccount-repo/main/latest/services/server/it-tools/compose.env` (core)
while the repo is executing the script on `${KOMODO_BASE_PATH}/data/repos/homelab` (periphery)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @joecksma on GitHub (Oct 19, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/927
Hello,
I want to use Repos scripts to use sops to decrypt my env files. This works as expected. But the decrypted files are not available to "Run Sync" and "Deploy Stack" Executions (as they seem to use the /repo-cache).
Is it intended that the scripts only edit the periphery copy and not the /repo-cache?
Example of an Error:
The file exists, but only under /data/repos/repo/services/server/it-tools/compose.env
My config
compose.yaml
komodo-config.toml
Thank you in advance for your help.
@jpod20 commented on GitHub (Oct 20, 2025):
I was running into the same issue but I think I discovered the solution. In the new compose files it no longer lists the repo-cache as a volume to be mounted. I removed it from my set up and I no longer receive that error.
https://github.com/moghtech/komodo/blob/main/compose/mongo.compose.yaml
@joecksma commented on GitHub (Oct 23, 2025):
I removed the repo cache from the volume mapping, but the behaviour is unchanged.
The Stack-UI reads the file from
/repo-cache/github.com/gitaccount-repo/main/latest/services/server/it-tools/compose.env(core)while the repo is executing the script on
${KOMODO_BASE_PATH}/data/repos/homelab(periphery)@Rustymage commented on GitHub (Oct 30, 2025):
I have this issue too.