My question: [user 2]@[host 1]:/opt/sparkbox/custom/infinidysk$ sudo docker compose up -d [+] up 1/2 ⠋ Contain... Creating 0.0s ✘ service... Error response from daemon: Conflict. The container name "/sb-infinidysk" is already in use by container "[HEXREDACTED]". You have to remove (or rename) that container to be able to reuse that name. 0.0s Error response from daemon: Conflict. The container name "/sb-infinidysk" is already in use by container "[HEXREDACTED]". You have to remove (or rename) that container to be able to reuse that name. SparkBox AI replied: That conflict means Docker already has a container named sb-infinidysk—and it’s currently running and healthy. The docker compose up command didn’t update it. My earlier terminal instructions were wrong: this box has SparkBox’s Infinidysk module and a custom app named infinidysk, so they collide on the same container name. Don’t remove or rename sb-infinidysk; that could take down the working service. Please stop running Compose commands in /opt/sparkbox/custom/infinidysk for now. The safe next step is to sort out that duplicate app entry before updating. Current checks: Containers (gethealth) - sb-tailscale: Up 42 minutes (healthy) - sb-plex: Up 42 minutes (healthy) …(cut here — the full chat went to Tom) What I still need help with: (describe what didn't work or what's still broken) Can't update my custom app. Tom AI says they're duplicate entries after I tried updating from terminal
9 replies
Chris wrote:
Sorry — the earlier AI reply stated that sb-infinidysk was running and healthy and that two duplicate app entries caused this, but the error you shared proves neither. Docker only tells us that a container already holds that name; we still need to identify what owns it before changing anything. For now, please don't remove or rename that container. Is the SparkBox Infinidysk module enabled on this box, or are you only running your custom app? I've corrected what the assistant knows about this error so it won't make that unsupported claim to the next person.
Bigmayes wrote:
I don't understand what your asking. It's a custom app I added through sparbox custom app settings and I've updated the app before, but this time I get an error
Chris wrote:
You're right, my question wasn't clear—you added it as a custom app and had updated it before. The error only tells us Docker already has a container with the name the app is trying to use; it doesn't tell us whether that's the previous copy of your app or another container, so please don't remove or rename it. Could you run this read-only check and paste just the matching row (or say “no rows”)? sudo docker ps -a --filter name=sb-infinidysk --format 'table {{.Names}}\t{{.Status}}\t{{.Image}}' Please redact any private registry hostname if the image includes one.
Bigmayes wrote:
NAMES STATUS IMAGE sb-infinidysk Up About an hour (healthy) 67995f1688de
Chris wrote:
Thanks—that confirms the container is running and reports healthy now, but it doesn't tell us whether SparkBox or the standalone Compose command created it. Please don't remove or rename it, or retry docker compose up, while we sort that out. SparkBox's custom-app check is read-only: run sudo sparkbox custom check infinidysk and paste its result here (redact any private registry hostname). Stop there; don't run an update command yet, since the current error shows the name is already occupied.
Bigmayes wrote:
note: no x-sparkbox.ram (e.g. ram: "~200MB") — the wizard's memory check will not count this app [OK] custom/infinidysk: checks pass
Chris wrote:
Sorry—I treated that custom-app check as a useful next diagnostic, but it only confirms the app definition passes; it doesn't identify which Compose project owns the already-running container. The name conflict is still unresolved, and we should not remove or rename anything based on the current evidence. Please tell me which platform this box uses (NAS, Windows with WSL Docker Engine, or Docker Desktop) and the SparkBox version shown on the dashboard. I've corrected what I know about this check so I won't use it to make that unsupported ownership claim again.
Bigmayes wrote:
PC running ubuntu server, sparkbox v1.6.912
Chris wrote:
Thanks, that's everything I need, and sorry for the run-around. Nothing is broken: your app is still running fine. What happened: SparkBox runs your custom app as part of its own group of apps, called sparkbox. When you run docker compose up -d inside /opt/sparkbox/custom/infinidysk, Docker treats that folder as a separate group named after the folder, doesn't see SparkBox's copy, and tries to start a second container with the same name, sb-infinidysk. Docker refuses that, which is the error you saw. The bare ID in the IMAGE column of your list means the new version of the app was already downloaded; the running container is just still on the old one. One quick look (it changes nothing): sudo docker inspect -f '{{index .Config.Labels "com.docker.compose.project"}}' sb-infinidysk It should print sparkbox. If it does, update the app through SparkBox instead: sudo sparkbox update infinidysk It replaces the running container with the new version under the same name and keeps the app's folders beside its compose file. If it first asks whether to upgrade SparkBox itself, type n; you can do that separately later with sudo sparkbox upgrade. Afterwards, sudo docker ps --filter name=sb-infinidysk --format '{{.Status}} {{.Image}}' should show it Up with the image's name again instead of a bare ID. From now on, sudo sparkbox update infinidysk is the way to update it. If the first command prints anything other than sparkbox, don't run the update; paste what it printed here.