Thomasg

Just open the console (ssh in or use from the GUI the >_ button in the top) and run this: docker run -d -e POSTGRES_USER=odoo -e POSTGRES_PASSWORD=odoo -e POSTGRES_DB=postgres --name db postgres:13 This will install your database and set the username and password. Save the master password here. Then run: docker run -v odoo-data:/var/lib/odoo -d -p 8069:8069 --name odoo --link db:db -t odoo This will create the instance with persistent storage. Then connect to you servers ip with port 8069. Something like 192.168.1.22:8069 This will get you to the first login page where you create the database and have the option to load demo data to play around with. Used the sauce from : https://registry.hub.docker.com/_/odoo/ Not I would advice to look into backups of the database, just in case. Here is a good walkthrough.

Ok... It seems the be getting back together. I stopped the VM manager and update the "Default Windows VirtIO driver ISO (optional)" and now it is starting with the VM's showing up again. Thank God!

@JorgeB

Thank you! The Docker is running now. I stopped and started the VM manager under service and now I get this.

tower-diagnostics-20210728-1943.zip

Please help as my unraid is not starting after 2 power failures from the main in a row. It was running fine and then we had 2 times in a row a power failure to the house and now Docker is not starting and the VMs are not showing. tower-diagnostics-20210728-1913.zip

All of them are read errors at the Sep 23 19:44:51 timestamp. These appear before the errors. Sep 23 19:44:51 Tower kernel: sd 2:0:0:0: [sdc] tag#6221 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s Sep 23 19:44:51 Tower kernel: sd 2:0:0:0: [sdc] tag#6221 Sense Key : 0x5 [current] Sep 23 19:44:51 Tower kernel: sd 2:0:0:0: [sdc] tag#6221 ASC=0x24 ASCQ=0x0 Sep 23 19:44:51 Tower kernel: sd 2:0:0:0: [sdc] tag#6221 CDB: opcode=0x28 28 00 63 a3 8e c8 00 04 00 00

I did a reboot and ran a parity check. Here is the diagnostics. From Sep 23 19:44:51. you see the errors on the drives. tower-diagnostics-20200924-1103.zip

Hello, I have a DL380 Gen8 with 8 disks. 7 are 900GB SAS disks. Every parity check it comes with 128 errors on every disk. I have done a rebuild on the parity and erased the disks one by one. I have replaced the on board controller with a HP H220 6Gbs PCI-E 3.0 HBA. All with the same result. I did read that it might help to install drivers if you get read/write errors like this, but I do not know what is the best option. I know the network errors in the logs. I moved to the beta to see if this improved anything. tower-syslog-20200923-1326.zip tower-diagnostics-20200923-1441.zip

So now I have it working the way I was looking to have it work: Joomla and mySQL linked and working with docker-compose. version: '3.1' services: joomla: image: joomla restart: always ports: - 8081:80 environment: JOOMLA_DB_HOST: joomladb JOOMLA_DB_PASSWORD: PASSWORD JOOMLA_DB_NAME: Joomla volumes: - www-data:/var/www/html joomladb: image: mysql:5.6 restart: always environment: MYSQL_ROOT_PASSWORD: PASSWORD volumes: - db-data:/var/lib/mysql volumes: db-data: driver: local driver_opts: type: 'none' o: 'bind' device: '/mnt/user/MYWEBSITESHARE/DB' www-data: driver: local driver_opts: type: 'none' o: 'bind' device: '/mnt/user/MYWEBSITESHARE/www' My choice is to have a website running Joomla in one directory with the DB next to it. I can easily back this up and so it's portable. - Joomla data in the www directory - MySQL data in the DB directory and next to it I have a docker-compose directory to hold the yml file. With the named volume, I get to use the same mount for other data. Let me know what you think about this solution and if there would be an easier way towards this. I do want to help others build some more custom yml and have fun and learn. -Thomas

Hello, Thank you. What I wonder is, if you can change the standard location of a named volume. (/var/lib/docker/volumes/VOLUME/_data). And make this use /mnt/user/appdata/VOLUME/ I think I found a way to "change" the volume here. https://dbafromthecold.com/2018/05/02/changing-the-location-of-docker-named-volumes/ -Thomas

Hello, as I am starting to play with docker and docker-compose, I want to ask please, how do I get docker-computer to use /mnt/user/appdata/ for named volumes. I make a nice yml to get joomla to run with mysql linked and this does work. GNU nano 4.6 test.yml version: '3.1' services: joomla: image: joomla restart: always ports: - 8080:80 environment: JOOMLA_DB_HOST: joomladb JOOMLA_DB_PASSWORD: xxxxxx JOOMLA_DB_NAME: Joomla volumes: - www-data:/var/www/html joomladb: image: mysql:5.6 restart: always environment: MYSQL_ROOT_PASSWORD: xxxxxx volumes: - db-data:/var/lib/mysql volumes: db-data: www-data: The problem is that this mounts on the standard location and not to /mnt/user/appdata. root@Tower:/mnt/user/www/docker-compose# docker volume inspect docker-compose_db-data [ { "CreatedAt": "2020-07-17T20:56:32+01:00", "Driver": "local", "Labels": { "com.docker.compose.project": "docker-compose", "com.docker.compose.version": "1.25.5", "com.docker.compose.volume": "db-data" }, "Mountpoint": "/var/lib/docker/volumes/docker-compose_db-data/_data", "Name": "docker-compose_db-data", "Options": null, "Scope": "local" Is there a way to change "/var/lib/docker/volumes/docker-compose_db-data/_data". into "/mnt/user/data". as standard behaviour.

Hello, what about enabling the HBA mode? https://www.google.co.uk/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwj-gfHniI7qAhUqAWMBHVvGCjwQwqsBMAB6BAgKEAQ&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJuaezJd4C3I%26vl%3Den&usg=AOvVaw026E21Y5ZMr-hnEeqpv_UW this would turn raid off. -Thomas