Backup error #79
Closed
opened 2026-02-04 18:15:44 +00:00 by ammaratef45
·
3 comments
No Branch/Tag Specified
main
renovate/docker-29.x
feature/makeDeleteDefault
restic-exporter
cmd-setup-restic-s3
prom-mon
feature/dockerfile
bb2-classic
feature/selective_paths
list
enable-label
backupbot_revolution
backup_volumes
multi_path
2.4.0+2.4.0
2.3.0+2.3.0-beta
2.2.0+2.2.1-beta
2.1.0+2.2.0-beta
2.0.1+2.1.1-beta
1.0.0+2.0.0-beta
0.2.0+1.0.0
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/backup-bot-two#79
Reference in New Issue
Block a user
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.
My backups stopped working couple of weeks ago and this is the error I see in the logs
Didn't have time to investigate yet but opening the issue so I don't forget to take a look, help welcome and appreciated!
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
@ammaratef45 @moritz if it is a non-swarm container then this would make the fix quite easy... 🙏
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 :)