When trying to use the openmediavault-compose plugin (version 6.0.2), pressing any button aside from those related to managing compose files (create/edit/delete) results in a following error:
400 - Bad Request
uuid: The value '' is not an UUIDv4.
openmediavault-compose error: 400 - Bad Request uuid: The value '' is not an UUIDv4.
-
Can you hit ctrl-shift-R and then post a screen shot of the list of compose files?
-
Also, did you set a shared folder in the settings tab first?
-
Also, did you set a shared folder in the settings tab first?
No, is it necessary?
-
No, is it necessary?
Yes. Otherwise, it won't know where to store the compose files. I guess I need to force it to be set.
-
Yes. Otherwise, it won't know where to store the compose files. I guess I need to force it to be set.
Oh, i see, thanks. I set up a new shared folder and it worked. Although i can't help but wonder why does it have to be a shared folder.
-
i can't help but wonder why does it have to be a shared folder.
What should it use? If you install the sharerootfs plugin, that shared folder could literally be any folder on the system.
-
What should it use? If you install the sharerootfs plugin, that shared folder could literally be any folder on the system.
I wanted to suggest allowing to simply choose a location in the root file system but then noticed that i have that sharerootfs plugin installed and read it's description. I still think that using a shared folder in this case is confusing. It is meant to be shared by definition and i'm not planning to share docker compose files with other users.
-
I still think that using a shared folder in this case is confusing.
Using shared folders as data locations for plugins is a primary concept of OMV.
I wanted to suggest allowing to simply choose a location in the root file system
If your OS disk fails, you lose your compose files.
It is meant to be shared by definition and i'm not planning to share docker compose files with other users.
You are assuming that shared means with other users. You can set permissions on a shared folder for only one user. Shared can also mean shared among services as well. Example: you could use rsync to backup your compose files to another shared folder. No user technically needs access to either shared folder.
-
If your OS disk fails, you lose your compose files.
Even before the compose plugin I would set my home folder in a shared folder on a data drive for this very reason. I’ve always wondered why the docker-compose [How-To]s by macom set the user’s home folder to /home/<user>:
Zitatin CLI:
- mkdir /home/docker1 create a folder for user docker1 in home directory
- mkdir /home/docker1/nextcloudcreate a folder where we will put the docker-compose.yml file to setup nextcloud
- cd /home/docker1/nextcloud change in that directory
- nano docker-compose.yml create an empty file and start the editor
-
I’ve always wondered why the docker-compose [How-To]s by macom set the user’s home folder to /home/<user>
Because I have backup
-
Same here, a Rsync Job cloning to a backup drive of the home folder and ALL docker-compose files are saved,
And also the docker root/container appdatas backed up and you won't fear any lost drive,
-
ALL docker-compose files are saved
That is the nice thing about the plugin if you use a data drive for compose file storage - if the os drive fails and you lose the omv database, you still have the compose files. If the data drive fails and you lose the compose files, you still have the omv database (which can recreate the compose files). Obviously backups fix everything : )
-
you still have the omv database (which can recreate the compose files).
Ok, it's printed on config.xml!!!
Nice to know,
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!