-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unraid Docker "Bad Parameter" #35
Comments
No, this is the right spot. What does your config.json look like? |
Hi I had this issue too, I noticed in the appdata/starbase folder that the following were created as folders rather than template files. config.json I had initially added my files into these folders and received the same bad parameters error. I deleted the folders and renamed my files accordingly (my logo to logo.png, fav to fav.ico, etc etc) and it seems to have worked. I'm unable to check the GUI yet as my works laptop blocks it but it is at least running successfully now. (I am a total novice to this so apologies if this is unclear or explains the obvious) |
I had this issue as well, I was able to correct it as @Tesseract23 did. Some extra details: Deploying from "APPS" in Unraid, if you do not add config.json, logo.png, and fav.ico to /mnt/user/appdata/starbase/ before clicking "APPLY" it creates folders in place of those files during the process: The docker run then fails because of these folders:
If you go to /mnt/user/appdata/starbase/ and delete/replace the folders with the proper files needed everything works perfectly even on a new installation of this. Maybe the solution is deploy examples in place of these files initially to avoid the failure and/or creation of directories with file names. Hope this helps! |
Apologies if this isn't the right spot for this, feel free to remove it if inappropriate. The Community Apps Docker in Unraid doesn't seem to be working. When starting it responds with "Execution Error. Bad Parameter". I've tried creating a basic config.json file but no cigar.
The text was updated successfully, but these errors were encountered: