Posts by jata1

For docker etc you want good quality fast and reliable data storage and access. For me I want to use ssd or similar for docker.

I have my os on an internal 64gb ssd. Had a free slot in the minipc. It has 95% free. Just omv os. I could put stuff on this disk but I don’t.

That would work with regular backups that you test can restore but you are just putting a lot of wear on the card I think.

If anything, switch to 32 or 16gb cards and don’t think about the unused space.

I would not use this for anything apart from the os.

in the compose plugin there is a schedule tab for backup. This will allow you to backup, update and prune your docker environment.

Pruning will remove old images. You can run this on a weekly schedule.

Use symlink plugin to create symlinks for the paths.

You need the -p flag on cp to preserve ownership and time stamps. The -a flag includes this

Use the cli and Linux copy (e. g. cp -a) or rsync -a command.

If you google these you will find lots of information.

Do a test of one small folder first. If happy with result do the main transfer

Thanks chente

I have read the doc end to end a long time ago when I setup docker. It’s a great doc 👍

Thank you. That’s great.

Nice you got it working. You have spent a load of time on this so happy days.

And we have learnt a limitation of mergerFS and docker so thanks Soma

I do have one more Feature Request for the compose plugin...

Would it be possible to add a stop & remove all running containers button in the Tools menu in Files page?

I can do this from the cli quite easily but I think it would be nice to have it available from the GUI

docker stop $(docker ps -a -q)
docker rm $(docker ps -a -q)

All good. Thanks ryecoaaron for the info and all the work you do on this plugin and everything else too.

I removed the * from the filter (left it blank) and ran the backup manually and it worked so I think I have found the issue. The * is not required so all is good.

I notice that you have added an exclusion for the backup. That is great. I was hoping to see that feature added to the plugin so thanks for this.

I have tested with exclusions and backups are correctly excluded but images are pulled for excluded containers. Would it be possible to change this behaviour so that the updates are not applied to excluded containers?

Thanks. Maybe it is the * I use in my schedule to backup all containers?

root@minipc:~# cat /etc/cron.d/omv-compose-update
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user    command
0 4 * * 7 root omv-compose-update-multi * >/dev/null 2>&1
root@minipc:~# cat /etc/cron.d/omv-compose-prune
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user    command
0 4 * * 7 root omv-compose-prune >/dev/null 2>&1
root@minipc:~#

Sorry I’m out of ideas.

What file system on the ssd where docker is installed?

Very strange error. I don’t think forcing user root will help.

Have you tried deleting the folder / data where opt is mounted locally?

I have a similar issue. I have always used a weekly backup and that works fine but I recently updated the config/job to update and prune.

The backup continues to work as expected but my containers are not updated.

I have looked at the logs and the update log (omv-compose-update) is empty and date stamp for the file is old so doesn't seem to be working

Might be user/file permission related.

Check your user for the container really is id 1000. Group id for users group will be 100.

Then check and update the file permissions for the container data using winSCP or use omv

I would get a new sd card. Install omv clean 64bit. Mount disk etc. will be worth it.

OMV regen is great if you have loads of config. I’m guessing you do not.

Upgrade will retain all of your config but do a backup of the install using the omv backup plugin using dd full disk first

Just tested this container/compose and works fine on my system so I think the issue is either:

1. corrupt image - delete and pull again

2. docker install issue on your system - try to reinstall docker?

Working compose below. Hope this helps.

services:
  kasm:
    image: lscr.io/linuxserver/kasm:latest
    container_name: kasm
    privileged: true
    environment:
      - KASM_PORT=4444
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /symlinks/omv-system/appdata/kasm/opt:/opt
    ports:
      - 3001:3000
      - 4444:4444
    restart: unless-stopped