Posts by trythat

    I did something similar, when I wanted the internal SATA port, I was using a small 60GB SSD drive and bought a USB to SATA cable and used that on 1 of the rear USB ports. I feel SSD's are a little more robust than a thumb drive, it's been working well since I made the change.

    Not with the way libvirt is creating the lxc container. I honestly don't know why you are doing this though. Running a container in a container is something I don't want to make changes for.


    I follow a youtube channel called @scottibyte and he explains as others have that a lxc container uses up less resources than a vm. He use docker within a lxc container a lot, I do understand to some extent why he does it.


    I've not tried it yet, as I've not seen many posts on here regarding lxc, which to me says either it's a little harder than using bare metal ubuntu and lxc, or people really just want to use docker an vms, which is pretty easy to do.


    The scottibyte channel is a good jumping in place to consider using lxc, very well put together tutorials. Plus I believe lxc is extremely popular with proxmox.


    I might actually have a go with my test vm for OMV and see what I can accomplish, probably more in the autumn/winter though, as I expect it might become a bit of a rabbit warren once I start playing with it :)

    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

    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.

    I changed Compose folder to root:users, and everyone.

    When I try and add container no files are saved to compose folder.


    Below is when doing 'Check'


    That is expected. The Delete button will delete the stop the compose, delete the compose file and env, delete the directory (not recursively), and then delete the database entry. If you undo that change, the database entry will be brought back which is all that is needed to recreate the dir and files it just deleted.


    I can't. By that time, the database entry would be gone and the saltstack code would know to delete it. I don't want the code to delete everything in that directory and recreate all compose files every time saltstack runs.

    Right, I understand that. I'm going to have lookup 'saltstack' as this seems to control a lot of what OMV does or allows.


    Quote

    What do you mean by "live"? When you click the save button in the edit window, it is writing to the database and then executing the saltstack code which should rewrite the compose and env files.


    In the above example, when I undo changes, the container still shows in the Files tab, but to recreate the container folder and yml files in the Compose folder, I have to click edit and save. And you can only click save after making some sort of change i.e adding or removing a space.

    I just thought if the folder was not in the Compose folder and the file window >1 character then the Save button could be used straight away.

    Quote

    Whenever the changes are applied right away (from the add or edit box), it doesn't keep the highlighted name. I can't change that behavior unless I change the plugin back to not applying the add or edit right away.

    OK, fair enough, I'd rather have the auto apply.

    I'll try and explain this the best way I can, please ask questions if need be. I don't remember seeing this bought up before, and it might be a very unusual problem, without an easy fix, I also think it might be a OMV one rather than this plugin.


    I've created a new container from within Files tab, here are the steps to reproduce, all from within Files Tab

    1. Press Down

    2. Press Delete, Yes

    3. Click undo changes, Yes


    Files tab still list container name.

    Compose folder does not have container name directory.


    But you can still click edit and make a change and save it.

    The plugin will then recreate the container folder in the Compose folder, you can then click 'Up' and all is well.


    Actually looking at it, it would seem as though the plugin should not delete folder until Apply changes have been confirmed.


    Also is there a reason why the 'Save' button can not be live as soon as you enter the edit window? Or at least be live if the character count >1?


    I know I asked this before, but it was when loads of questions was coming your way. Almost all the actions that work on a highlighted name in Files tab, keep the highlight on after completing the action i.e 'check', I know they use a pop out box, and edit does not, but could the name stay highlight after using edit?

    • Typing # BACKUP at the end of the line that defines a volume will include that volume in the backup

    I've been out of the forum for a couple of days, which means I've missed a bit, this plugin is changing at a rapid pace :) I know when you me were testing the backup/restore, ryecoaaron did say that '# BACKUP' would Backup even if the volume was larger than the max value in setting, is this still the case?

    You shouldn't do tests like this on your production system, use virtual machines. If it breaks you lose nothing.

    It is also easy to do tests, take a snapshot of the clean version, if it breaks, you just need to restore from the snapshot and retry, it takes a minute to do it.

    Yeah I know, I used to enjoy computing on the edge :) But the more I thought of it, the more I thought there's KVM in OMV use it! And as you say there's the snapshot thing as well, I'm just spinning up a VM now.

    It could but that would make all backups unlimited. Adding a comment to the volume # BACKUP would force it regardless of size.  # SKIP_BACKUP will skip no matter what.

    Example:

    Code
          - /tmp/test3:/test3 # BACKUP
          - /tmp/test4:/test4
          - /tmp/test5:/test5 # SKIP_BACKUP
          - /tmp/test6:/test6

    Ah, I got you, when creating volumes in the files.yml, you'd add the above.


    Again it's 1 of those things that might not crop up very often, I did try backing up 2 containers and it worked ok, still not sure if I wanted 0=unlimited for a couple of containers and 1GB for the rest, I'd just create 2 jobs. But I might want unlimited for all containers, thats a lot of comments to add.


    Personally, I'm not sure I'd want much more than my compose files, and my appdata folder. My CCTV and media are on drives of their own. At the moment I just backup my 1TB ssd to a backup 2TB NVME with a few other folders and then syncthing somewhere else.


    Quote

    Are you running these tests on an important system??

    I am, I've done this loads of times, I have backups of what I think is important, and sometimes a breakage is just what is needed, to get a better system. In my window days, I also rebuilt my system at the least every 6 months.



    But I think I might spin up a simple OMV VM, as it wasn't quite as enjoyable as in the old days (this getting older is a pain) :) In fact I'm going to do that now! Thanks for the push.

    sudo apt-get -f install