Skip to content
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

Open
xKOBAYASHIMARUx opened this issue Oct 22, 2024 · 3 comments
Open

Unraid Docker "Bad Parameter" #35

xKOBAYASHIMARUx opened this issue Oct 22, 2024 · 3 comments

Comments

@xKOBAYASHIMARUx
Copy link

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.

@notclickable-jordan
Copy link
Owner

No, this is the right spot.

What does your config.json look like?

@Tesseract23
Copy link

Tesseract23 commented Dec 10, 2024

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
logo.png
fav.ico

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)

@bmoorelucas
Copy link

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:
image

The docker run then fails because of these folders:

docker run
-d
--name='starbase'
--net='bridge'
--pids-limit 2048
-e TZ="America/Chicago"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="WHITEVISION"
-e HOST_CONTAINERNAME="starbase"
-e 'TITLE'='Avengers'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:4173]'
-l net.unraid.docker.icon='https://i.imgur.com/dMTz5iU.png'
-p '4173:4173/tcp'
-v '/mnt/user/appdata/starbase/config.json':'/app/src/config.json':'rw'
-v '/mnt/user/appdata/starbase/fav.ico':'/app/public/favicon.ico':'rw'
-v '/mnt/user/appdata/starbase/logo.png':'/app/public/logo.png':'rw'
-v '/mnt/user/appdata/starbase/icons':'/app/public/icons':'rw' 'jordanroher/starbase-80'
f86e7cd8283e3d9107be809fd6831864b3fe9393a6dbc4fbacc37f2213363cd3
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/user/appdata/starbase/config.json" to rootfs at "/app/src/config.json": mount /mnt/user/appdata/starbase/config.json:/app/src/config.json (via /proc/self/fd/6), flags: 0x5000: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type.

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants