/container print
0 ;;; Process exited with status 1
name="f47c1f39-b38c-45f8-bb1f-d78ea300af42" repo="adguard/adguardhome:latest" os="linux" arch="arm" interface=virteth1 root-dir=adguard mounts=adguard_etc workdir="/opt/adguardhome/work" start-on-boot=yes status=stopped
RB4011iGS+5HacQ2HnDWhat device is this ?
Are you sure the CORRECT folder exists ?
Do you mean like on the screenshot? If so, what about the tag? I set it via the terminal. In principle, I have all the commands saved specifically so that the tags are the same. But I once tried to recreate it and my settings were not saved. But I recreated it in the terminal. Although maybe I did not do it in exactly the right order. And I am also confused by the name of the container. Now it is f47c1f39-b38c-45f8-bb1f-d78ea300af42. The new one, in theory, will have a different name.OK, if you are sure that folder is 100% correct.
Another thing to try:
Open container so you have all settings in front of you.
Create a new container in a second dialog box with the exact same settings, don't save yet (I do so with copy-paste between 2 dialog boxes).
Throw away the first container.
Then commit creation of new container.
It should take over all settings from the previous one.
Unfortunately, I didn't succeed and had to reconfigure. Perhaps I did something wrong. I'll have to try to create a similar situation myself sometime and try to restore the settings. But I have some doubts about the tags. This time, for some reason, the container was created with a different tag.Tag is what your file should be when creating.
I've done this plenty of times, name of the container doesn't matter as long as it uses the same folders as the previous container.
As a matter of fact, when you want to upgrade a container, you need to do something similar when doing it manually. Throw away the old one and create a new one with the same settings.
Fair enough. More saying it's a 50/50% shot it the root-dir (*perhaps higher since there are more files) & if root-dir corrupted, that's easily replaced since it a container that one is "safe". The mount often store config files, so if the corruption is there...well, now you have data loss or need to have backup.I had case where file was corrupted in mount dir, because service was writing some file in it. So if such files are not recreated there, issue can still persist if is such case.
Unfortunately, there were no copies. Some time ago I was interested here on the forum how to create copies or settings files for Adguard, but no one suggested anything, and I myself was unable to configure it.copy config files from backup into mounted dirs (you have it, right?)
From time to time I swap the UPS and just for a few days the Mikrotik stood without it.Also consider using UPS if you are often experiencing power outages
Yes, I could go to the catalog. I am attaching a screenshot to finally understand whether I understand you correctly. And I did not delete the mount point. These settings remained and were even picked up in the configuration window. I only deleted the container, but this did not save the settings (block lists, local domain names, etc.)Can you see the files in the mount?
... If so, you should be able to just delete the container - not the mount. And create a new one, using same VETH and mount as before. In fact, if "copy" before deleting, you'll have all the setting to re-create it (perhaps needing to specify the tag).
Why does the root-dir NOT have a path on it? That means it's going to RouterOS flash/etc that's limited in size....
/system resource print
uptime: 1d39m27s
version: 7.18.2 (stable)
build-time: 2025-03-11 11:59:04
factory-software: 6.43.2
free-memory: 829.8MiB
total-memory: 1024.0MiB
cpu: ARM
cpu-count: 4
cpu-frequency: 1200MHz
cpu-load: 4%
free-hdd-space: 308.2MiB
total-hdd-space: 512.0MiB
write-sect-since-reboot: 51519
write-sect-total: 1844804
bad-blocks: 0%
architecture-name: arm
board-name: RB4011iGS+5HacQ2HnD
platform: MikroTik
There is simply no other. I would be happy to use a USB or SSD drive, but this model does not have such connectors.still not recommended to run containers on internal drive.
Not using AdGuard but by simply reading instructions for "Create directories for persistent configuration and data" from its container documentation https://hub.docker.com/r/adguard/adguardhome#quickstart it seems that /opt/adguardhome/conf and /opt/adguardhome/work directories contains configuration files (not sure to what is your adguard_etc mount pointing, but it seems wrong by its name - /etc maybe, there must be 2 mounts for mentioned dirs by their doc) and from this dirs files can be copied locally for backup after each config change, eg. using sftp to ROS, since you mentioned that you are using WinSCP to browse container files, you can backup/restore files from these 2 dirs using it.Unfortunately, there were no copies. Some time ago I was interested here on the forum how to create copies or settings files for Adguard, but no one suggested anything, and I myself was unable to configure it.
I also read this page but I still didn't understand which files are responsible for the configuration. They also wrote that you can attach a file with a list of sites that need to be blocked, but I also didn't understand how to connect them. I tried, but it didn't work.Not using AdGuard but by simply reading instructions for "Create directories for persistent configuration and data" from its container documentation https://hub.docker.com/r/adguard/adguardhome#quickstart it seems that /opt/adguardhome/conf and /opt/adguardhome/work directories contains configuration files (not sure to what is your adguard_etc mount pointing, but it seems wrong by its name - /etc maybe, there must be 2 mounts for mentioned dirs by their doc) and from this dirs files can be copied locally for backup after each config change, eg. using sftp to ROS, since you mentioned that you are using WinSCP to browse container files, you can backup/restore files from these 2 dirs using it.