Backup error #79

Closed
opened 2026-02-04 18:15:44 +00:00 by ammaratef45 · 3 comments
Owner

My backups stopped working couple of weeks ago and this is the error I see in the logs

2025-12-15T03:30:03.231724484Z {"filename": "backup", "lineno": 34, "process": 416171, "message": "Uncaught exception", "exc_info": "Traceback (most recent call last):\n File "/usr/bin/backup", line 550, in \n cli()\n File "/usr/lib/python3.11/site-packages/click/core.py", line 1157, in call\n return self.main(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3.11/site-packages/click/core.py", line 1078, in main\n rv = self.invoke(ctx)\n ^^^^^^^^^^^^^^^^\n File "/usr/lib/python3.11/site-packages/click/core.py", line 1688, in invoke\n return _process_result(sub_ctx.command.invoke(sub_ctx))\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3.11/site-packages/click/core.py", line 1434, in invoke\n return ctx.invoke(self.callback, **ctx.params)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/lib/python3.11/site-packages/click/core.py", line 783, in invoke\n return __callback(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File "/usr/bin/backup", line 100, in create\n app_settings = parse_backup_labels()\n ^^^^^^^^^^^^^^^^^^^^^\n File "/usr/bin/backup", line 206, in parse_backup_labels\n stack_name = labels['com.docker.stack.namespace']\n ~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nKeyError: 'com.docker.stack.namespace'", "message_type": "CRITICAL"}

Didn't have time to investigate yet but opening the issue so I don't forget to take a look, help welcome and appreciated!

My backups stopped working couple of weeks ago and this is the error I see in the logs > 2025-12-15T03:30:03.231724484Z {"filename": "backup", "lineno": 34, "process": 416171, "message": "Uncaught exception", "exc_info": "Traceback (most recent call last):\n File \"/usr/bin/backup\", line 550, in <module>\n cli()\n File \"/usr/lib/python3.11/site-packages/click/core.py\", line 1157, in __call__\n return self.main(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/lib/python3.11/site-packages/click/core.py\", line 1078, in main\n rv = self.invoke(ctx)\n ^^^^^^^^^^^^^^^^\n File \"/usr/lib/python3.11/site-packages/click/core.py\", line 1688, in invoke\n return _process_result(sub_ctx.command.invoke(sub_ctx))\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/lib/python3.11/site-packages/click/core.py\", line 1434, in invoke\n return ctx.invoke(self.callback, **ctx.params)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/lib/python3.11/site-packages/click/core.py\", line 783, in invoke\n return __callback(*args, **kwargs)\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/bin/backup\", line 100, in create\n app_settings = parse_backup_labels()\n ^^^^^^^^^^^^^^^^^^^^^\n File \"/usr/bin/backup\", line 206, in parse_backup_labels\n stack_name = labels['com.docker.stack.namespace']\n ~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\nKeyError: 'com.docker.stack.namespace'", "message_type": "CRITICAL"} Didn't have time to investigate yet but opening the issue so I don't forget to take a look, help welcome and appreciated!
ammaratef45 added the
bug
help wanted
labels 2026-02-04 18:15:44 +00:00
Owner

The key here is KeyError: 'com.docker.stack.namespace'
Do you have some non coop-cloud container running on this machine? Maybe a duplicate of this one:
#72

The key here is `KeyError: 'com.docker.stack.namespace'` Do you have some non coop-cloud container running on this machine? Maybe a duplicate of this one: https://git.coopcloud.tech/coop-cloud/backup-bot-two/issues/72
Owner

@ammaratef45 @moritz if it is a non-swarm container then this would make the fix quite easy... 🙏

@ammaratef45 @moritz if it is a non-swarm container then this would make the fix quite easy... 🙏
Author
Owner

OMFG, so I was inspecting for this and found a service called secret-reader, which is created outside of coop-cloud and had access to one of my admin secrets for one of the recipes

After a crazy couple of hours of investigating how I was hacked (because how else did that happen), I looked at the history of my commands and when seeing the context of what else I ran at that same day it is clear that was def me hacking at my server!

phew, thanks both, I'll close this issue as a duplicate and will reopen it if the error comes back by the time of the next backup :)

OMFG, so I was inspecting for this and found a service called secret-reader, which is created outside of coop-cloud and had access to one of my admin secrets for one of the recipes After a crazy couple of hours of investigating how I was hacked (because how else did that happen), I looked at the history of my commands and when seeing the context of what else I ran at that same day it is clear that was def me hacking at my server! phew, thanks both, I'll close this issue as a duplicate and will reopen it if the error comes back by the time of the next backup :)
Sign in to join this conversation.
No description provided.