github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-05-06 00:18:38 -05:00
Code Issues 3.5k Packages Projects Releases 103 Wiki Activity

[GH-ISSUE #727] 1.18.4 error: #2394

New Issue
Closed
opened 2026-04-11 10:18:37 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-11 10:18:37 -05:00
Owner
Copy Link

Originally created by @eitch on GitHub (Aug 11, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/727

1.18.3 worked perfectly, upgrading to 1.18.4 made all stacks fail with this error:

ERROR: failed to parse response to json | type: ComposePull | request: ComposePull { stack: Resource {
....

    TRACE:
	1: error decoding response body
	2: missing field `missing_files` at line 1 column 321
Originally created by @eitch on GitHub (Aug 11, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/727 1.18.3 worked perfectly, upgrading to 1.18.4 made all stacks fail with this error: ``` ERROR: failed to parse response to json | type: ComposePull | request: ComposePull { stack: Resource { .... TRACE: 1: error decoding response body 2: missing field `missing_files` at line 1 column 321 ```
GiteaMirror commented 2026-04-11 10:18:38 -05:00
Author
Owner
Copy Link

@mbecker20 commented on GitHub (Aug 19, 2025):

Must also update periphery version to match core version, same when updating to 1.19.0

<!-- gh-comment-id:3202241890 --> @mbecker20 commented on GitHub (Aug 19, 2025): Must also update periphery version to match core version, same when updating to 1.19.0
GiteaMirror commented 2026-04-11 10:18:39 -05:00
Author
Owner
Copy Link

@MP-Tool commented on GitHub (Aug 21, 2025):

Must also update periphery version to match core version, same when updating to 1.19.0

I addressed this issue in the PR #748 . issue resolved

<!-- gh-comment-id:3208600610 --> @MP-Tool commented on GitHub (Aug 21, 2025): > Must also update periphery version to match core version, same when updating to 1.19.0 I addressed this issue in the PR #748 . issue resolved
GiteaMirror commented 2026-04-11 10:18:39 -05:00
Author
Owner
Copy Link

@eitch commented on GitHub (Aug 21, 2025):

ahh, yes, my bad.

I installed periphery with

curl -sSL https://raw.githubusercontent.com/moghtech/komodo/main/scripts/setup-periphery.py | python3

I want to now use Ansible for upgrades: Do i need to remove the previous installation? Or does the ansible role detect the existing installation and just upgrade it?

<!-- gh-comment-id:3209383703 --> @eitch commented on GitHub (Aug 21, 2025): ahh, yes, my bad. I installed periphery with ``` curl -sSL https://raw.githubusercontent.com/moghtech/komodo/main/scripts/setup-periphery.py | python3 ``` I want to now use Ansible for upgrades: Do i need to remove the previous installation? Or does the ansible role detect the existing installation and just upgrade it?
GiteaMirror commented 2026-04-11 10:18:40 -05:00
Author
Owner
Copy Link

@MP-Tool commented on GitHub (Aug 21, 2025):

No need to remove the previous installation.

The setup script is designed to be run multiple times safely - it won't overwrite your existing config. The Ansible role is smart enough to detect existing installations and will simply upgrade the binary while keeping all your settings intact.

Just run the Ansible role with komodo_action: "update" and you're good to go. It'll stop the service, replace the binary, and restart with your existing configuration. 🦎

<!-- gh-comment-id:3209980669 --> @MP-Tool commented on GitHub (Aug 21, 2025): No need to remove the previous installation. The setup script is designed to be run multiple times safely - it won't overwrite your existing config. The Ansible role is smart enough to detect existing installations and will simply upgrade the binary while keeping all your settings intact. Just run the Ansible role with komodo_action: "update" and you're good to go. It'll stop the service, replace the binary, and restart with your existing configuration. 🦎
GiteaMirror commented 2026-04-11 10:18:40 -05:00
Author
Owner
Copy Link

@eitch commented on GitHub (Aug 21, 2025):

The setup script is designed to be run multiple times safely - it won't overwrite your existing config. The Ansible role is smart enough to detect existing installations and will simply upgrade the binary while keeping all your settings intact.

Just run the Ansible role with komodo_action: "update" and you're good to go. It'll stop the service, replace the binary, and restart with your existing configuration. 🦎

I tried that, but since i installed periphery with root, it didn't work. I didn't see how to change the ansible to use the same installation.

<!-- gh-comment-id:3209998680 --> @eitch commented on GitHub (Aug 21, 2025): > The setup script is designed to be run multiple times safely - it won't overwrite your existing config. The Ansible role is smart enough to detect existing installations and will simply upgrade the binary while keeping all your settings intact. > > Just run the Ansible role with komodo_action: "update" and you're good to go. It'll stop the service, replace the binary, and restart with your existing configuration. 🦎 I tried that, but since i installed periphery with root, it didn't work. I didn't see how to change the ansible to use the same installation.
GiteaMirror commented 2026-04-11 10:18:41 -05:00
Author
Owner
Copy Link

@MP-Tool commented on GitHub (Aug 21, 2025):

The setup script is designed to be run multiple times safely - it won't overwrite your existing config. The Ansible role is smart enough to detect existing installations and will simply upgrade the binary while keeping all your settings intact.
Just run the Ansible role with komodo_action: "update" and you're good to go. It'll stop the service, replace the binary, and restart with your existing configuration. 🦎

I tried that, but since i installed periphery with root, it didn't work. I didn't see how to change the ansible to use the same installation.

The issue: You installed Periphery with the setup script (as root/system-wide) but want to switch to Ansible management. The Ansible role is an external community project that defaults to user-mode installation, which conflicts with your root installation, I think.

Quick fix: For now, just upgrade with the setup script:

curl -sSL https://raw.githubusercontent.com/moghtech/komodo/main/scripts/setup-periphery.py | python3 - --version=v1.18.4

To switch to Ansible management, you have two options:

  1. Uninstall first, then use Ansible:
  • Stop and disable: systemctl stop periphery && systemctl disable periphery
  • Remove: /usr/local/bin/periphery, /etc/systemd/system/periphery.service
  • Then run Ansible role in user-mode
  1. Configure Ansible for root:
komodo_user: "root"
komodo_bin_dir: "/usr/local/bin"
komodo_config_dir: "/etc/komodo" 
komodo_service_dir: "/etc/systemd/system"

Note: Running as root is less secure, refer to Docker Rootless

The Ansible role is a community project, so configuration issues should be reported there: Ansible-Role-Komodo

<!-- gh-comment-id:3210385959 --> @MP-Tool commented on GitHub (Aug 21, 2025): # > > The setup script is designed to be run multiple times safely - it won't overwrite your existing config. The Ansible role is smart enough to detect existing installations and will simply upgrade the binary while keeping all your settings intact. > > Just run the Ansible role with komodo_action: "update" and you're good to go. It'll stop the service, replace the binary, and restart with your existing configuration. 🦎 > > I tried that, but since i installed periphery with root, it didn't work. I didn't see how to change the ansible to use the same installation. The issue: You installed Periphery with the setup script (as root/system-wide) but want to switch to Ansible management. The Ansible role is an external community project that defaults to user-mode installation, which conflicts with your root installation, I think. Quick fix: For now, just upgrade with the setup script: ``` curl -sSL https://raw.githubusercontent.com/moghtech/komodo/main/scripts/setup-periphery.py | python3 - --version=v1.18.4 ``` To switch to Ansible management, you have two options: 1. Uninstall first, then use Ansible: - Stop and disable: `systemctl stop periphery && systemctl disable periphery` - Remove: `/usr/local/bin/periphery`, `/etc/systemd/system/periphery.service` - Then run Ansible role in user-mode 2. Configure Ansible for root: ``` komodo_user: "root" komodo_bin_dir: "/usr/local/bin" komodo_config_dir: "/etc/komodo" komodo_service_dir: "/etc/systemd/system" ``` Note: Running as root is less secure, refer to [Docker Rootless](https://docs.docker.com/engine/security/rootless/) The Ansible role is a community project, so configuration issues should be reported there: [Ansible-Role-Komodo](https://github.com/bpbradley/ansible-role-komodo)
GiteaMirror commented 2026-04-11 10:18:42 -05:00
Author
Owner
Copy Link

@eitch commented on GitHub (Aug 21, 2025):

Thanks a lot for your help. I will probably switch to user mode, which certainly makes more sense.

<!-- gh-comment-id:3210406920 --> @eitch commented on GitHub (Aug 21, 2025): Thanks a lot for your help. I will probably switch to user mode, which certainly makes more sense.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
2.0.0
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
v2
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#2394
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?