What better features?
sorry, the translation tool I used didn't seem to work well. I want to express that I am looking forward to omv providing us with more and better functions in the future.
(eg:But a more readable error log would be more newbie friendly. The idea seems unrealistic)
I am looking forward to omv providing us with more and better functions in the future.
OMV or the kvm plugin? What functions are you looking for?
But a more readable error log would be more newbie friendly. The idea seems unrealistic
For OMV or the kvm plugin?
OMV or the kvm plugin? What functions are you looking for?
For OMV or the kvm plugin?
For OMV。
For more specific things, I only have some simple ideas, such as the operation of multiple FILE in the Compose plug -in, and performing "up" and "down" in batches.
In the ZFS plug -in, it can provide a regularly -built (delete) file snapshot function.
Portainer and Yacht can set their own Volume positions.
But I am not sure if these ideas are meaningful to most people.
For more specific things, I only have some simple ideas, such as the operation of multiple FILE in the Compose plug -in, and performing "up" and "down" in batches.
This one might not be hard. I will look into it.
In the ZFS plug -in, it can provide a regularly -built (delete) file snapshot function.
Have you looked into zfs-auto-snapshot?
Portainer and Yacht can set their own Volume positions.
Use a compose file in the compose plugin if you want to set volumes for these containers.
Have you looked into zfs-auto-snapshot?
Sorry, I didn't see it, was it achieved through Scheduled Tasks?
Use a compose file in the compose plugin if you want to set volumes for these containers.
Yes, I did the same. I mean that I hope to provide options in the "System ->omv extras ->Portainer" of the Web UI. I feel that this function of the Web UI will be more complete.（Maybe to remove the functions on the webui and increase the guidance of exmple in the compose plug -in, I think it is also good, but it may not be friendly to novices.）
was it achieved through Scheduled Tasks?
I assume so. I don't use it myself.
I mean that I hope to provide options in the "System ->omv extras ->Portainer" of the Web UI.
I knew that is what you were asking for but I don't think it is needed and would complicate things for noobs. Why do you want to set the path for the volume? portainer and yacht store very little. Basically just the compose files and I think the compose plugin is better for that. Not only does it store the compose files in the omv database, it writes them to files on a data disk. Automatic backup : )
Maybe to remove the functions on the webui and increase the guidance of exmple in the compose plug -in, I think it is also good, but it may not be friendly to novices.
I thought about this as well but until we have better docs, I think it should stay as it is.
I think you need to add the "whois" package to your OMV install. As openwrt does run:
Good catch. While I did add that dependency, I didn't push out a new package. I will push a new package out later.
I knew that is what you were asking for but I don't think it is needed and would complicate things for noobs. Why do you want to set the path for the volume? portainer and yacht store very little. Basically just the compose files and I think the compose plugin is better for that. Not only does it store the compose files in the omv database, it writes them to files on a data disk. Automatic backup : )
I also think the Compose plug-in is great. If you can optimize the batch operation and add the intuitive image management function, I think for many people, you can no longer need the portal.
My personal usage habit (I don't know how others do it). I put the Docker volume in a unified directory and back it up. As a docker, I think the volume of the portainer should be with other dockers.
albicocca I think you need to add the "whois" package to your OMV install. Other things might not run, but openwrt does:
Thank you very much. In fact, I have installed "whois" before, but the installation of openwrt failed. Just after seeing your message, I successfully installed it again. I don't understand why. Is it because of reboot? XD
add the intuitive image management function
What do you want to manage about the images?
As a docker, I think the volume of the portainer should be with other dockers.
You should be backing up the OS as well. And portainer isn't really data like your other containers. It is more of tool like OMV. Either way, I don't want to add paths to omv-extras. If this is needed, people will have to use the compose plugin.
What do you want to manage about the images?
I hope to have a list showing the existing images, which can pull the specified images with basic management functions such as deletion.
During my use, some dockers cannot use the latest version completely, and may also use "nightly" "develop" or specific version numbers.
I have encountered some situations. For example, when comparing the new version of qbittorrent, errors will occur, while the old version is normal. I use the same configuration and switch between two images to find problems.
After some images are updated, the old versions cannot be deleted normally (until now, I don't know the reason). Finally, they are deleted through some troublesome operations. If there is an image management function, I can at least visually see the existence of old versions of images.
I keep getting the attached error anytime I try to start an LXC container. Any initial troubleshooting I can do?
I hope to have a list showing the existing images, which can pull the specified images with basic management functions such as deletion.
During my use, some dockers cannot use the latest version completely, and may also use "nightly" "develop" or specific version numbers.
You are doing it wrong. If you specify a version in your compose file, it will pull the same image you would pull in a management tab. I don't mind adding a prune menu (system, image, volume, container, network options) but I don't see why some of this management needs to be done.
Check the path is correct ..... missing / at start of path.
The plugin adds it if it is missing because I can't change the behavior of the directory chooser. https://github.com/OpenMediaVa…/engined/rpc/kvm.inc#L991
Any initial troubleshooting I can do?
Please use the bell in the upper right to copy&paste the error message. Your screenshot doesn't show all of the error. But from what I can see, it is failing to download the image from linuxcontainers.org. Make sure your dns is working on your OMV system and make sure your network isn't blocking linuxcontainers.org.
You are doing it wrong. If you specify a version in your compose file, it will pull the same image you would pull in a management tab. I don't mind adding a prune menu (system, image, volume, container, network options) but I don't see why some of this management needs to be done.
Yes, I can pull to the specified version, I want to express the later problem. "down" or "delete" on an existing yml will not delete an existing image. If I have multiple versions of the image installed, unwanted images will be left on the device. I think the webui needs at least a function to delete images.
"down" or "delete" on an existing yml will not delete an existing image. If I have multiple versions of the image installed, unwanted images will be left on the device. I think the webui needs at least a function to delete images.
prune will do that. docker image prune will probably do a better job cleaning up than a user would.
prune will do that.
That's a good idea, could you add a button in the compose plug-in to activate this directive? (like "apt clean" in the System -- >omv-extras -- >Settings screen
Sorry, I thought maybe relying too much on the web user interface, which I thought would be easier to use. It's helpful for people who know even less about linux than I do.
Please use the bell in the upper right to copy&paste the error message. Your screenshot doesn't show all of the error. But from what I can see, it is failing to download the image from linuxcontainers.org. Make sure your dns is working on your OMV system and make sure your network isn't blocking linuxcontainers.org.
The full error is below. The omv machine does have working DNS and can reach linuxcontainers.org. Thanks for the help!
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; wget -qO- https://images.linuxcontainers.org/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz | tar xJ -C /srv/dev-disk-by-uuid-76f4ccf2-ad92-4313-ba2e-259476a90313/lxc/' with exit code '2':
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; wget -qO- https://images.linuxcontainers.org/images/ubuntu/kinetic/amd64/default/20221115_07:43/rootfs.tar.xz | tar xJ -C /srv/dev-disk-by-uuid-76f4ccf2-ad92-4313-ba2e-259476a90313/lxc/' with exit code '2': in /usr/share/php/openmediavault/system/process.inc:217
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/kvm.inc(2854): OMV\System\Process->execute(Array, 2)
#1 /usr/share/openmediavault/engined/rpc/kvm.inc(1182): OMVRpcServiceKvm->downloadImage('ubuntu;kinetic;...', '/srv/dev-disk-b...')
#2 [internal function]: OMVRpcServiceKvm->setVm(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('setVm', Array, Array)
#5 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'setVm', Array, Array, 1)
#6 {main}Don’t have an account yet? Register yourself now and be a part of our community!