添加链接
link管理
链接快照平台
  • 输入网页链接,自动生成快照
  • 标签化管理网页链接

All you have to do is specify the file in the compose file - https://docs.docker.com/compos…ile/05-services/#env_file

I do several test and do not works as described or I do something bad.


I copy my Variables.env to root of compose:



I use this yaml file for webDAV as example:

omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


omv-extras.org plugins source code and issue tracker - github - changelogs


Please try ctrl-shift-R and read this before posting a question.

Please put your OMV system details in your signature.
Please don't PM for support... Too many PMs!

omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


omv-extras.org plugins source code and issue tracker - github - changelogs


Please try ctrl-shift-R and read this before posting a question.

Please put your OMV system details in your signature.
Please don't PM for support... Too many PMs!

That is the OMV way. I don't have anyway to sync the database if you edit outside the plugin. Is there a reason to edit the file outside of the plugin?

Not really, apart from in vs-code I have a tab for 'global.env' open. But TBH I expect a global file is not going to be edited very often. Also in the compose files there is a warning, but not in 'global.env', just dotting i's and crossing t's.

This will not work. The plugin will overwrite it. You must copy & paste the variables from your file into the global env editor. If you don't, the next time you make a change in the plugin, it will overwrite your file.

Sorry, I really think that I do it, but my memory is really bad, thanks to remember the correct way.

Also in the compose files there is a warning, but not in 'global.env', just dotting i's and crossing t's.

I didn't add the auto generated header to the global.env file for the same reason I removed it from the regular .env file creation for the Files tab - it causes issues for some things. I would have to find the post with an example of how it causes problems. It was reported by a couple of users. But you shouldn't rely on that header. If a file is maintained by something in OMV, you are most likely not able to make changes from the command line.

omv 7.0.5-1 sandworm | 64 bit | 6.5 proxmox kernel

plugins :: omvextrasorg 7.0 | kvm 7.0.11 | compose 7.1.3 | k8s 7.1.0-3 | cputemp 7.0 | mergerfs 7.0.3


omv-extras.org plugins source code and issue tracker - github - changelogs


Please try ctrl-shift-R and read this before posting a question.

Please put your OMV system details in your signature.
Please don't PM for support... Too many PMs!

If people use it how I think they will, they will be editing every time they add a container/compose.


I think this is how I intend to use this feature - For 'global.env' I've setup a few variables i.e. PGUD that I use often, plus folders I use regularly i.e media, downloads etc. Then if I wanted something like passwords for cameras, I will then add that to the container.env file.


But as with most things PC related there is rarely just one way to do it :) As long as it works for me, I'm a happy bunny.


I didn't add the auto generated header to the global.env file for the same reason I removed it from the regular .env file creation for the Files tab - it causes issues for some things. I would have to find the post with an example of how it causes problems. It was reported by a couple of users. But you shouldn't rely on that header. If a file is maintained by something in OMV, you are most likely not able to make changes from the command line.


OK, I'm getting used to hearing 'That is the OMV way.' :) <3

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden Um die Webseite zu verbessern und maß­geschneiderte Werbung anzubieten werden Cookies verwendet. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen Schließen