Error Adding New Set #132
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm so frustrated with myself mostly for not being able to figure this out, but after the last update, I'm having an issue trying to add sets. I ended up deleted everything and starting fresh and I still cannot figure out what I am doing wrong. I am getting the following error when trying to add sets, no matter what set I try to add:
Error: Error while importing set 10311-1: [Errno 2] No such file or directory: '/app/sets/10311-1.jpg'I am running BrickTracker on Unraid. I was able to overcome all of my issues prior to the current version but I think I am at the point where I need help.
Here is the command execution upon editing all of the available variables:
I see the issue, this is related to breaking changes made in v1.3 where the default folder paths were consolidated.
Version 1.3 consolidated all user data into a single
data/folder.static/sets/',static/parts/`, etc.data/sets/,data/parts/, etc.This was done to consolidate all user data (database, images, instructions, CSVs) into one folder for consistent backups.
Your Docker volumes are mounted to
/app/static/*(the old v1.2 paths):But your
BK_SETS_FOLDERenvironment variable is set to justsets(a relative path), which BrickTracker v1.3+ interprets as/app/data/sets/(the new default) - hence the "No such file or directory" error.Option 1: Update Environment Variables
Keep your existing volume mounts but tell BrickTracker to use the old paths:
These need to match your volume mount points inside the container.
Option 2: Migrate to New Structure (Recommended)
Follow the migration guide to update your volume mounts to the new
data/structure. This gives you a single volume for all data.The migration guide explains both approaches and helps you choose which is best for your setup. This should resolve your issue!
I don't see any references to 'static' in the configuration after a few tweaks.
Previously (v1.2.4 and earlier), folders (e.g.
BK_SETS_FOLDER) were relative to/app/static/. From version 1.3 onward, folders are relative to/app/.For example, with:
BK_SETS_FOLDER=sets:/app/static/sets/app/setsBecause of this change, the new default is:
which resolves to:
From the CHANGELOG:
The migration guide visualizes this change clearly with folder structure diagrams.
Please make sure that the folders referenced in your Docker command actually exist:
Your database path
/data/app.dbis absolute to your host system, meaning BrickTracker is looking for it at:not relative to
/app(i.e. not/app/data/app.db).Based on your Docker command, these are the paths BrickTracker is trying to access:
If you want to use the
/app/data/folder (recommended for v1.3 and newer), update your Docker command to:With this change, the resolved paths will be:
Hope it helps!
I think I am back up and running. Once I made those changes, I ran into issues with the DEFAULT_ORDER variables. The default configuration for the Unraid Community App has some errors.
Thank you!!!
Glad you got it working. You don't need to setup all the env vars. You can skip the ones you don't want to use. The default values will apply.