Running the latest Komodo docker images on Debian.
I created a stack for automation workloads, starting with Home Assistant. It worked well, but after changing a volume mount in the compose file and pushing it to the GitHub repo I can no longer Pull or Deploy.
Any suggestions for further troubleshooting?
When selecting Pull Images the following error is shown:
ERROR: request to periphery failed |500 Internal Server Error
TRACE:
1: Stopped after repo pull failure
The Komodo core log shows:
2025-03-08T09:20:58.643077Z INFO ExecuteRequest{req_id=500937c1-c20a-481a-8a4d-02f68b293118 user_id="67c9ca36f55d64ebf731089c"update_id="67cc0bfa600b476f389e6e6d"request="PullStack"}: core::api::execute: /execute request 500937c1-c20a-481a-8a4d-02f68b293118 | user: **REDACTED**
2025-03-08T09:20:58.995784Z WARN ExecuteRequest{req_id=500937c1-c20a-481a-8a4d-02f68b293118 user_id="67c9ca36f55d64ebf731089c"update_id="67cc0bfa600b476f389e6e6d"request="PullStack"}: core::api::execute: /execute request 500937c1-c20a-481a-8a4d-02f68b293118 error: request to periphery failed |500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:20:58.995849Z WARN core::api::execute: /execute request 500937c1-c20a-481a-8a4d-02f68b293118 task error: request to periphery failed |500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:25:31.980787Z WARN core::api::write::stack: Failed to pull latest images for Stack monitoring | request to periphery failed |500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:25:32.326525Z WARN core::api::write::stack: Failed to pull latest images for Stack jelly | request to periphery failed |500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:25:32.650778Z WARN core::api::write::stack: Failed to pull latest images for Stack automation | request to periphery failed |500 Internal Server Error: Stopped after repo pull failure
And the Periphery log:
2025-03-08T09:20:29.314437Z INFO periphery: Komodo Periphery starting on http://0.0.0.0:8120
2025-03-08T09:20:30.255191Z WARN periphery::router: request 12a822dd-4520-49ae-8eef-77c8305e098f | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:20:30.595068Z WARN periphery::router: request d73a4b82-bc6c-496a-998b-c089f346fa3e | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:20:30.950800Z WARN periphery::router: request b083bc06-43f9-416b-990c-b00c044a4d63 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:20:31.302806Z WARN periphery::router: request 0cbfec06-c738-47cd-98bc-5a580b93a462 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:20:31.642140Z WARN periphery::router: request 6f4c64d6-df70-4c2b-ac56-de2a72817180 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:20:45.572436Z WARN periphery::router: request a668e2ff-d5e3-4780-906e-e7c2a222630a | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:20:58.995287Z WARN periphery::router: request 81b486a9-06e5-40fc-b2cf-d5a69109e839 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:21:00.594299Z WARN periphery::router: request 0b0aca34-b6ab-4082-9d89-7df882110e9c | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:21:15.599889Z WARN periphery::router: request 46a71323-aa25-4474-9c31-bf807a422c59 | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
I don't understand where the repeated error: Repo path is not directory. is it cloned? comes from.
UPDATE: Interestingly, when I do Deploy instead of Pull image there is no error; it deploys just fine (safe some issue within the container volumes I need to fix).
The periphery log however still gets 'flooded' with error: Repo path is not directory. is it cloned? for all my created stacks.
Originally created by @crazyelectron-io on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/349
Running the latest Komodo docker images on Debian.
I created a stack for automation workloads, starting with Home Assistant. It worked well, but after changing a volume mount in the compose file and pushing it to the GitHub repo I can no longer Pull or Deploy.
Any suggestions for further troubleshooting?
When selecting **Pull Images** the following error is shown:
```shell
ERROR: request to periphery failed | 500 Internal Server Error
TRACE:
1: Stopped after repo pull failure
```
The Komodo core log shows:
```shell
2025-03-08T09:20:58.643077Z INFO ExecuteRequest{req_id=500937c1-c20a-481a-8a4d-02f68b293118 user_id="67c9ca36f55d64ebf731089c" update_id="67cc0bfa600b476f389e6e6d" request="PullStack"}: core::api::execute: /execute request 500937c1-c20a-481a-8a4d-02f68b293118 | user: **REDACTED**
2025-03-08T09:20:58.995784Z WARN ExecuteRequest{req_id=500937c1-c20a-481a-8a4d-02f68b293118 user_id="67c9ca36f55d64ebf731089c" update_id="67cc0bfa600b476f389e6e6d" request="PullStack"}: core::api::execute: /execute request 500937c1-c20a-481a-8a4d-02f68b293118 error: request to periphery failed | 500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:20:58.995849Z WARN core::api::execute: /execute request 500937c1-c20a-481a-8a4d-02f68b293118 task error: request to periphery failed | 500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:25:31.980787Z WARN core::api::write::stack: Failed to pull latest images for Stack monitoring | request to periphery failed | 500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:25:32.326525Z WARN core::api::write::stack: Failed to pull latest images for Stack jelly | request to periphery failed | 500 Internal Server Error: Stopped after repo pull failure
2025-03-08T09:25:32.650778Z WARN core::api::write::stack: Failed to pull latest images for Stack automation | request to periphery failed | 500 Internal Server Error: Stopped after repo pull failure
```
And the Periphery log:
```shell
2025-03-08T09:20:29.314437Z INFO periphery: Komodo Periphery starting on http://0.0.0.0:8120
2025-03-08T09:20:30.255191Z WARN periphery::router: request 12a822dd-4520-49ae-8eef-77c8305e098f | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:20:30.595068Z WARN periphery::router: request d73a4b82-bc6c-496a-998b-c089f346fa3e | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:20:30.950800Z WARN periphery::router: request b083bc06-43f9-416b-990c-b00c044a4d63 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:20:31.302806Z WARN periphery::router: request 0cbfec06-c738-47cd-98bc-5a580b93a462 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:20:31.642140Z WARN periphery::router: request 6f4c64d6-df70-4c2b-ac56-de2a72817180 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:20:45.572436Z WARN periphery::router: request a668e2ff-d5e3-4780-906e-e7c2a222630a | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:20:58.995287Z WARN periphery::router: request 81b486a9-06e5-40fc-b2cf-d5a69109e839 | type: ComposePull | error: Stopped after repo pull failure
2025-03-08T09:21:00.594299Z WARN periphery::router: request 0b0aca34-b6ab-4082-9d89-7df882110e9c | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
2025-03-08T09:21:15.599889Z WARN periphery::router: request 46a71323-aa25-4474-9c31-bf807a422c59 | type: GetLatestCommit | error: Repo path is not directory. is it cloned?
```
I don't understand where the repeated `error: Repo path is not directory. is it cloned?` comes from.
The Komodo configuration toml:
```toml
[[server]]
name = "homeserver"
[server.config]
address = "http://periphery:8120"
region = "Home"
enabled = true
##
[[stack]]
name = "automation"
[stack.config]
server = "homeserver"
project_name = "automation"
poll_for_updates = true
run_directory = "./stacks/automation"
git_provider = "GitHub.com"
git_account = "crazyelectron-io"
repo = "crazyelectron-io/homeserver"
ignore_services = ["init-ha"]
environment = """
HOME_ASSISTANT_PG_USER = [[HOME_ASSISTANT_PG_USER]]
HOME_ASSISTANT_PG_DB = [[HOME_ASSISTANT_PG_DB]]
HOME_ASSISTANT_PG_PASSWORD = [[HOME_ASSISTANT_PG_PASSWORD]]
HOME_ASSISTANT_DOMAIN = [[HOME_ASSISTANT_DOMAIN]]
"""
```
And finally the GitHub repo:
```ini
.
├── README.md
└── stacks
├── automation
│ ├── compose.yaml
│ └── config
│ ├── configuration.yaml
│ └── get-hacs.sh
└── monitoring
├── compose.yaml
└── config
├── config.alloy
├── loki.yaml
└── prometheus.yaml
```
UPDATE: Interestingly, when I do `Deploy` instead of `Pull image` there is no error; it deploys just fine (safe some issue within the container volumes I need to fix).
The `periphery` log however still gets 'flooded' with `error: Repo path is not directory. is it cloned?` for all my created stacks.
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 @crazyelectron-io on GitHub (Mar 8, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/349
Running the latest Komodo docker images on Debian.
I created a stack for automation workloads, starting with Home Assistant. It worked well, but after changing a volume mount in the compose file and pushing it to the GitHub repo I can no longer Pull or Deploy.
Any suggestions for further troubleshooting?
When selecting Pull Images the following error is shown:
The Komodo core log shows:
And the Periphery log:
I don't understand where the repeated
error: Repo path is not directory. is it cloned?comes from.The Komodo configuration toml:
And finally the GitHub repo:
UPDATE: Interestingly, when I do
Deployinstead ofPull imagethere is no error; it deploys just fine (safe some issue within the container volumes I need to fix).The
peripherylog however still gets 'flooded' witherror: Repo path is not directory. is it cloned?for all my created stacks.