Lately, Gordon has become nearly unusable for me. It ignores explicit instructions, fails to follow rules, deletes files, and has even removed entire containers after being told not to delete anything. Even simple tasks can send it into a loop that leaves things worse than before. It used to be extremely effective and solve problems quickly, but over the past couple of months its behavior has steadily declined. Has anyone else noticed this, and is there a reliable way to prevent it from making destructive changes?
3 Answers
I’m not very technical, so I used to describe the problem and let Gordon fix the container. That worked well for a while, but over the last two months it has become increasingly unreliable and now regularly makes things worse.
For more predictable results, use the regular command-line tools and follow the official documentation instead of relying on Gordon. It may take a little longer, but you have much more control over each operation.
Some people have had a decent experience with Gordon, but its behavior seems inconsistent. For anything important, keep backups and avoid giving it permission to make destructive changes automatically.
That’s what I’m doing from now on. Gordon has been wasting more time and resources than it saves.