Migrated from louislam/dockge, get SQLITE missing 'name' column error when adding an external dockge Agent

[Drakonas]

I updated the louislam/dockge:1 compose.yaml to cmcooper1980/dockge:latest for my two dockge instances. They booted up independently just fine.

But there's one issue: I can't add the other as a separate Agent. I get this error:

insert into `agent` (`name`, `password`, `url`, `username`) values ('', '[redacted]', 'http://192.168.1.213:5001', 'myuser') - SQLITE_ERROR: table agent has no column named name

It looks like your version has a new column for agent names, but it didn't update the database with the column. louislam's version doesn't have this column in the db.

Based on this stackoverflow post, "When you add a column and don't use onUpdate method, existing tables don't have the new column added. This is not to say that you should use onUpdate every time you change your schema during development- onUpdate should be used when you actually release a new version of your app."

Hoping @cmcooper1980 can add some insight, as I can't use external agents with this repo, without this column being added.

[cmcooper1980]

Please confirm you don't have any critical unused volumes that you're saving for some reason, IF you do, create a backup and/or modify the following commands to specifically remove the associated dockge volume only, if it exists. I only mention this as I did not have any issues moving from louislam's official to my fork seems same is true at least for @Angrite #31

if in current dockge compose file directory:
docker compose down
docker system prune -a -f --volumes (-f suppresses confirmation, modify this line as needed if concerned about unused volumes)
docker compose pull
docker compose up -d --force-recreate --remove-orphans

from any directory (point to compose file):
docker compose -f location/dockge/compose down
docker system prune -a -f --volumes (-f suppresses confirmation, modify this line as needed if concerned about unused volumes)
docker compose -f location/dockge/compose pull
docker compose -f location/dockge/compose up -d --force-recreate --remove-orphans

Also, as a workaround/test, modify your compose and just have it point to a new/fresh config location. The DB doesn't store much in way of configuration so most you'll have to do is recreate the login

[Drakonas]

if in current dockge compose file directory: docker compose down docker system prune -a -f --volumes (-f suppresses confirmation, modify this line as needed if concerned about unused volumes) docker compose pull docker compose up -d --force-recreate --remove-orphans

I ended up just adding the column to the sqlite db myself to fix, which somehow made it work permanently on my master agent. And I can stop/start stacks just fine.

But I can't seem to recreate the steps for my remote agent. It always breaks when I stop a stack, whether from the master UI or from the native remote agent UI directly. I am sure I did the steps the same order, but I can't figure it out.

Also, as a workaround/test, modify your compose and just have it point to a new/fresh config location. The DB doesn't store much in way of configuration so most you'll have to do is recreate the login

I've done this multiple times. The master is not having this name issue anymore. But my remote agent is, even though I have them configured the same. They just have different stacks. I'm not sure what's going on.