TerraMaster Forum

well, you could create scheduled job that will run on NAS Power off, with custom script something like this: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/Volume1/@apps/virtualbox/lib /usr/lib/virtualbox/VBoxManage controlvm <vmid> acpipowerbutton use the same vmid that you used for auto start from Virtu...

Here's how to:
viewtopic.php?f=73&t=5169

Hi all! Here are steps that will allow you to run VM on system boot. Requirements: [*] SSH connection to NAS [*] VirtualBox VM that's up and running Steps: Connect to your NAS via SSH . Now, you need to find your VM ID, simple ps command with grep will do: ps -eo command | grep VBoxHeadless Output w...

Everything seems to be working OK now, didn't have to do anything but wait for few minutes after docker was updated Did immich update which pulled new containers and everything was working OK without need to run chmod as before. Checked perms on /etc/hosts and /etc/resolv.conf, both now have permiss...

this will do:
I've noticed that crontab is not persistent after reboot...

to make it simpler, here are few steps that will: create fixPerms.sh script (find all etc/resolv.conf and etc/hosts files in docker containers and apply chmod 644) make script executable add script crontab and run every minute # Create script cat <<EOF > fixPerms.sh #!/bin/bash DOCKER_VOLUME=$(df --...

just change resolv.conf to hosts in my script from previous post and it will do the trick

it's not a permanent solution, that's why I've said create cron job

anyway, TM should either provide us with steps how to add users to acl or just leave everything 644

Thank you!!!... i works, but still i have a very strange problem, if i try to resolve "localhost" inside a container it's return an error: mastercontainer:/var/www/docker-aio# nslookup localhost Server: 127.0.0.11 Address: 127.0.0.11:53 ** server can't find localhost: NXDOMAIN ** server c...

I've made a script that will change permissions of all container resolv.conf files to 644, as they should be. This will fix DNS resolving when running containers with users that are not root (eg. arr apps) I have tried playing with group / user permissions via TOS GUI, but in the end the simplest so...