[transfert a docker application to another unraid machine]

how to do it ?

 

is creating the docker app in the another unraid and copying the appdata associated is enough ?

 

[docker , share, tar incremental , pb]

hi,

subject : cannot do a tar incremental on a share linked to a docker.

 

so , i have a share connected to a docker ( piwigo ) , and when i do a  tar with incremental option, it doesn't work.

Another share with a copy of the same files , no pb.

i tried with the docker stopped , same effect.

 

Can someone explain to me the reason why ?

 

Regards,

Pascal

[[Support] knex666 - Nextcloud]

On 5/31/2020 at 1:09 AM, knex666 said:

Hi, 

 

this docker does not contain any database, please install a separate docker contaiber for you database and connect it in the Installation process, this is very easy. 

 

Cheers

THX.

[[Support] knex666 - Nextcloud]

hi knex666

is the docker install MariaDB ?

 

i installed 3 days ago for test with sqllite , was working but the install of onlyoffice document  server was missing !!!

So did a new install and was trying with MariaDB but got error.

 

by the way , continued with sqllite and now i have onlyoffice document  server running.

 

regards,

pascal

 

[vm debian upgrade]

hi,

what would be the best way to upgrade a VM debian from stretch to buster ?

 

thx

Pascal

[Preclear plugin]

hi !

First : thank you for this plugin

 

second: Could you add the name of the system in the email subject status report ?

i was pre-clearing 2 drives in 2 differents system at the same time and couldn't know which system it was in the email.

 

thx.

[Unraid updates failing]

yes you are right  ,

i could have use a unassigned devices drive , but since i  was using a terminal screen , i did not think about it , was not on a df listing !!!

same using an array disk !!!

 

next time !!

 

in fact , the biggest pb is everything works so well, that you do not touch and forget .

 

Pascal

 

 

 

[Unraid updates failing]

hello,

i had the same pb yesterday, trying to go from 6.3.2 to 6.5.3.

i have the same rootfs size : 867M used 700M.

After  tracking the pb to not enough space in /tmp for download and unzip.

my solution was to move /tmp to /boot because i have 7G available there ( i know i was using the usb stick for that)

 

[do not copy, if you do not understand]

mv /tmp to /tmpori  (rename tmp)

ln -s /tmp /boot/tmp  (create a link from /tmp to /boot/tmp)

mkdir /boot/tmp

 

tested by touch /tmp/toto , ls -l /boot/tmp , ok the file toto is present

cp -R * /tmpori /tmp ( recopy old tmp to new tmp)

 

and there upgrade , everything went fine , reboot , OK , restart array , OK.

 My new rootfs is  : rootfs          867M  703M  165M  81% /

 

i think i will have to do the same for each upgrade, since i have only 2G memory and no pb for a file server only purpose.

 

[unRAID OS version 6.4.0 Stable Release Available]

On 1/26/2018 at 2:26 PM, pgnyc said:

hello, so i have a pb with an upgrade to 6.4.0 from 6.3.5 .

a VM slackware  64 14.2 has a kernel panic at startup.

 

the server is new, i just created 2 VM , a debian and a slackware, they were up and running on 6.3.5 .

that's all i did not even started to do something with them just created an started.

with 6.4.0 , the debian VM is still running ok.

but not the slackware. the boot screen is ok , the kernel start but panic immediately.

if try to create another VM ,  i have the grub page and nothing more after.

 

here diagnostic and screnshoot.

 

Pascal.

 

 

 

NEWS :

so i tried with cpu mode = QEMU and now it's working.

why the original setting is  not working ( host passthrough )  ?

 

On 1/26/2018 at 2:26 PM, pgnyc said:

 

 

aserv1-diagnostics-20180126-1411.zip

 

[unRAID OS version 6.4.0 Stable Release Available]

hello, so i have a pb with an upgrade to 6.4.0 from 6.3.5 .

a VM slackware  64 14.2 has a kernel panic at startup.

 

the server is new, i just created 2 VM , a debian and a slackware, they were up and running on 6.3.5 .

that's all i did not even started to do something with them just created an started.

with 6.4.0 , the debian VM is still running ok.

but not the slackware. the boot screen is ok , the kernel start but panic immediately.

if try to create another VM ,  i have the grub page and nothing more after.

 

here diagnostic and screnshoot.

 

Pascal.

 

 

 

Templates

aserv1-diagnostics-20180126-1411.zip