limetech Posted September 12, 2014 Share Posted September 12, 2014 Download Disclaimer: This is beta software. While every effort has been made to ensure no data loss, use at your own risk! This build includes a patched 3.16.2 kernel that solves the ReiserFS file corruption issue introduced with -beta7 (linux kernel 3.16.0). We have been in correspondence with the guy who introduced the bug and also created the patch and his statement regarding the patch is: "I believe the patch 100% fixes the problem." If you are running unRAID OS 6-beta7 or -beta8 please update immediately to this release. Further, we are in continuing discussion to find out if we can characterize the nature of file system corruption. As soon as we have some information to report, we will report it. Along with supporting btrfs, xfs, and reiserfs, in a future release we will add ext4 option as well. Other changes in this release are mainly bug fixes and subsystem version updates. We did include adding back auto-expand of file systems when upgrading smaller device to larger device. unRAID Server Version 6.0-beta9 Release Notes ============================================= Please note: THIS IS BETA SOFTWARE. WHILE EVERY EFFORT HAS BEEN MADE TO ENSURE NO DATA LOSS, USE AT YOUR OWN RISK. Summary of changes from 6.0-beta8 to 6.0-beta9 ---------------------------------------------- - btrfs-progs: update to 3.16 - docker: fix bug which can cause creation of volume file to fail on user share - emhttp: auto-expand all file system types (btrfs, reiserfs, xfs) - libvirt: update to 1.2.8 - linux: update to 3.16.2 (with 3.16 reiserfs corruption fix patch) - php: update to 5.4.32 including PTS support - shfs: fixed improper handling of global share cache floor - slack: rc.docker: handle restart following Docker daemon crash - slack: rc.docker: remove extraneous sync's - slack: replace sysklog package with rsyslog 8.4.0 - unraid: permit "md_write_method" to be set via mdcmd - unraid: fix overlapped i/o detection race condition - webGui: plgMan: fix 'plugin' update method - webGui: plgMan: handle stale and error plugin install - webGui: integrated gfjardim's latest excellant dockerMan plugin - xen: update to 4.4.1 Summary of changes from 6.0-beta7 to 6.0-beta8 ---------------------------------------------- - docker: update to 1.2.0 docker for unRAID works with loopback mounted btrfs image integrate forum user "gfjardim" docker plugin (with permission) - emhttp: fix handling of blank 'min free space' share setting - emhttp: use 'mkdir -p' instead of 'mkdir' when creating disk mount points - shfs: honor cache floor settings for 'unsplittable' paths - plgMan: support unRAID OS update via Plugins page - webGui: change Utilities menu to Tools, added Credits, license info Summary of changes from 6.0-beta6 to 6.0-beta7 ---------------------------------------------- - btrfs-progs: update to 3.14.2 - docker: update to 1.1.2 - emhttp: assign any number of slots to array and cache pool - emhttp: implemented multi-device btrfs cache pool feature - emhttp: support btrfs, reiserfs, xfs filesystems for array devices - emhttp: handle multiple key files in /boot/config, but no more keys files in /boot - emhttp: add indicator for shares that only exist on the cache - libvirt: update to 1.2.7 - linux: update to 3.16 CONFIG_NR_CPUS: changed from 16 to 256 CONFIG_XFS_FS: include XFS file system CONFIG_XFS_POSIX_ACL: include XFS ACL support add "pci: Enable overrides for missing ACS capabilities" patch (for KVM vfio/PCI pass-through) - misc: console coloring for kool kids - php: update to 5.4.30 add support for curl, openssl, zlib, bz2 and gmp - qemu: update to 2.1.0 add "Enable -cpu option to hide KVM" patch (for Nvidia) - samba: update to 4.1.11 - shfs: fixed improper handling of cache floor - slack: added htop-1.0.2 - slack: added xfsprogs-3.1.11 - unraid: correct overlapped I/O logic in driver; remove write-throttling algorithm - webGui: add "check filesystem" functions on DiskInfo page. - webGui: several misc. bug fixes Known issues in this release ---------------------------- - emhttp: removed automatic file system expand when small drive is replaced by bigger drive. This will be put back in next release. - emhttp: certain btrfs pool operations can cause mount to take a looooong time - slack: bonding driver interaction with dhcpcd is flaky, introduced delay as workaround. - slack: the time setting "(UTC+10:00) Brisbane" is wrong: Brisbane does not use daylight savings time like "(UTC+10:00) Camberra, Melbourne, Sydney". - slack: no 32-bit executable support (a non-issue?) - netatalk: update to 3.1.x didn't happen yet - webGui: help incomplete; a few rough edges remain - emhttp: any file that is world-readable is accessible via http://Tower/mnt/... (which is to say a file can be made non-accessible by making it non-world-readable). Summary of changes from 6.0-beta5a to 6.0-beta6 ----------------------------------------------- - docker: added support for docker 1.0.0 - emhttp: support btrfs-formatted cache disk - linux: update to 3.15.0 - linux: added more features: CONFIG_NR_CPUS: changed from 8 to 16 (number of CPU's supported) CONFIG_NUMA: Enable NUMA (Non Uniform Memory Access) support. CONFIG_SCSI_MVSAS_TASKLET: Support for interrupt tasklet (improves mvsas performance) CONFIG_ALX: Qualcomm Atheros AR816x/AR817x support CONFIG_I40E: Intel(R) Ethernet Controller XL710 Family support CONFIG_AMD_IOMMU: AMD IOMMU support CONFIG_INTEL_IOMMU: Support for Intel IOMMU using DMA Remapping Devices CONFIG_INTEL_IOMMU_DEFAULT_ON: Enable Intel DMA Remapping Devices by default CONFIG_IRQ_REMAP: Support for Interrupt Remapping CONFIG_VFIO: VFIO Non-Privileged userspace driver framework CONFIG_VFIO_PCI: VFIO support for PCI devices CONFIG_VFIO_PCI_VGA: VFIO PCI support for VGA devices CONFIG_CIFS_SMB2: SMB2 network file system support CONFIG_NET_9P: Plan 9 Resource Sharing Support (9P2000) CONFIG_NET_9P_VIRTIO: 9P Virtio Transport CONFIG_9P_FS: Plan 9 Resource Sharing Support (9P2000) CONFIG_9P_FS_POSIX_ACL: 9P POSIX Access Control Lists CONFIG_MAGIC_SYSRQ - slack: updated packages with security advisories: curl-7.36.0 gnutls-3.1.25 ntp-4.2.6p5 openssh-6.6p1 openssl-1.0.1h openssl-solibs-1.0.1h shadow-4.1.5.1 libtasn1-3.6 php-5.4.29 samba-4.1.6 - slack: added packages: btrfs-progs libcgroup sqlite - slack: minor fixes in rc.S, rc.M, rc.sshd - qemu: version 2.0.0 with SeaBIOS 1.7.5 - xen: update to 4.4.0, with security patches through 6-13-2014. Eliminated qemu-system-i386 altogether and now just builds qemu-system-x86-64 (qemu 2.0.0) Correct typo in /etc/default/xendomains. Summary of changes from 6.0-beta4 to 6.0-beta5a ----------------------------------------------- - emhttp: fix issue generating ini files with single quotes in keys - emhttp: support BRSTP variable to enable/disable network bridge STP - openssl: update to openssl-1.0.1g (heartbleed bug fix) - php: update to 5.4.26, and change search path for php.ini to: /etc/php change search path for additional ini files to: /etc/php/conf.d in /etc/php/php.ini include this directive: auto_prepend_file="/usr/local/emhttp/plugins/webGui/include/local_setup.php" local_setup.php defines the timezone and locale so that php scripts don't have to - slack: initialize /etc/ssl/certs using update-ca-certificates - sysinfo: added line to display OpenSSL version - webGui: Network Settings: add control for BRSTP Summary of changes from 6.0-beta3 to 6.0-beta4 ---------------------------------------------- - linux: added more features: CONFIG_BLK_DEV_SR: SCSI CDROM support DEVPTS_MULTIPLE_INSTANCES: Support multiple instances of devpts SCSI_MPT3SAS: LSI MPT Fusion SAS 3.0 Device Driver VT_HW_CONSOLE_BINDING: Support for binding and unbinding console drivers CONFIG_SENSORS_F71805F: Fintek F71805F/FG, F71806F/FG and F71872F/FG support CONFIG_SENSORS_F71882FG: Fintek F71882FG and compatibles support CONFIG_SENSORS_F75375S: Fintek F75375S/SP, F75373 and F75387 support - nfs: fixed issue where exported volumes were read-only (needed to explicitly add sec=sys option) - php: added json support - samba: update to 4.0.15 in order to set "acl allow execute always" to "yes" in order to fix windows exe files not executing - samba: "max protocol = SMB3" is the new default - slack: added ca-certificates - slack: added nano editor - slack: added usb-utils (lsusb command) - smartmontools: update to 6.2 - syslinux: remove Xen command line options (user can tune syslinux.cfg via webGui) - emhttp: fixed bug where blank value for cache 'Min free space' would cause shfs terminate - emhttp: fixed bug where changing SMB export setting in Active Directory mode caused crash - emhttp: provide $_GET and $_POST to php scripts - emhttp: when root password set, only authentiate webGui page access - emhttp: very simple security for http access to share data (a work in process) - emhttp: return correct mime type per file extension - webGui: add syslinux configuration page on 'flash' menu - webGui: add plugin manager - webGui: add xen domain manager - webGui: current list of built-in plugins: indexer - Share Browser sysinfo - The 'Info' button plgMan - Plugin Manager vendor - third party utility components webGui - the webGui itself xenMan - Xen Manager - xen: update to 4.3.2 Summary of changes from 6.0-beta2 to 6.0-beta3 ---------------------------------------------- - flash: added Xen boot options, multiboot support - linux: added drivers: CONFIG_PATA_AMD: support for the AMD and NVidia PATA interfaces found on the chipsets for Athlon/Athlon64. CONFIG_PATA_ATIIXP: support for the ATI ATA interfaces found on the many ATI chipsets. CONFIG_PATA_OLDPIIX: support for early PIIX PATA support. CONFIG_PATA_PDC2027X: support for Promise PATA pdc20268 to pdc20277 host adapters. CONFIG_PATA_VIA: support for the VIA PATA interfaces found on the many VIA chipsets. CONFIG_SENSORS_NCT6775: support for the hardware monitoring functionality of the Nuvoton NCT6775F, NCT6776F, NCT6779D and compatible Super-I/O chips. - linux: fixed issue with hwclock (added RTC support which somehow got left out) - linux: updated Intel e1000e driver to 2.5.4 - slack: added more packages, notably python and perl - slack: added network bridging, including bridge of bonded ethernet NICs - webGui: added bridge control on Network Settings page - Xen: 4.3.1 Summary of changes from 6.0-beta1 to 6.0-beta2 ---------------------------------------------- - slack: added missing library: libtasn1 - vsftp: fixed - webGui: updated to 2014.01.24a to fix issue with updating Summary of changes from 5.x to 6.0-beta1 ---------------------------------------- - linux: version 3.10.24p x86_64 (includes reiserfs 'continuous write' patch) - linux: include all KVM/Xen virtualization options, including libvirt - linux: back to using kernel realtek NIC driver r8169 - mailx: version 12.5 - php: upgrade to 5.4.20 - samba: upgrade to 4.0.9 - slack: upgrade to slackware64-14.1 - openssh: version 6.3p1. Host keys are generated and stored in /boot/config/ssh directory. Currently configured to allow null passwords (easy to change). telnet still enabled (easy to disable). - webGui: upgrade to webGui-master Upgrade Instructions ==================== If you are currently running any previous 6.0-beta -------------------------------------------------- In general it is only necessary to copy these files from the zip file to the root of your USB Flash device: bzimage bzroot xen readme.txt Starting in -beta8, docker is configured to make use of a loop mounted image file for its operation. This may require you to re-download your docker containers. Starting in -beta7, if your Plus or Pro key is located in the root of your USB Flash device you must move it to the 'config' directory in order for it to be recognized. If you are currently running unRAID Server OS release 5.0.x ----------------------------------------------------------- First backup the content of your USB Flash device to a folder on your PC and then install this release according to "Installation on a New Flash Device" below. Before ejecting your flash, restore the 'config' directory from your back up. If you are currently running any unRAID Server OS release before 5.0: --------------------------------------------------------------------- First upgrade to latest 5.x release. Please refer to upgrade instructions on our wiki: http://lime-technology.com/wiki/index.php/Upgrade_Instructions Installation on a New Flash Device ================================== To make a bootable USB Flash device follow these steps: If using Windows (XP/Vista/Win7) -------------------------------- 1. Plug your USB Flash device into your Windows PC. 2. Open 'My Computer' (XP) or 'Computer' (Vista/Win7) and right-click your Flash device. Click 'Format...', set the volume label to UNRAID and then click 'Start'. Important: the volume label must be set exactly to UNRAID (all caps). 3. Click on your Flash device (to open it), click on the zip file (to open it) and drag then entire contents of the unRAID Server zip file to the Flash. 4. For Windows XP, click on the file 'make_bootable'. A DOS window will open and run the 'syslinux' utility on the Flash. For Windows Vista or Windows 7, right-click on the file 'make_bootable' and select 'Run as administrator'. The 'syslinux' utility will write the Master Boot Record and create a small hidden file named 'ldlinux.sys' on the Flash device, making it bootable. 5. Once again, right-click your Flash device in 'My Computer' or 'Computer' and then click 'Eject'. Your USB Flash device is now ready to boot into unRAID Server OS. If using Mac OS X ----------------- 1. Plug your USB Flash device into your Mac. 2. Open Disk Utility, select the device and click the Erase tab. Select Format: MS-DOS (FAT) format, Name: UNRAID and then click Erase. Important: the Name (volume label) must be set exactly to UNRAID (all caps). 3. Click on your UNRAID device (to open it), click on the downloaded unRAID Server OS release zip file (to open it), click on the un-archived unRAID Server folder that results (to open it), and drag then entire contents of the unRAID Server folder to the Flash. 4. Click on the file 'make_bootable_mac' on the device. A terminal window will open and prompt for your admin password. If the selected device is correct, enter the password and hit return. The script will proceed to run the 'syslinux' utility which will write the Master Boot Record and create a small file named 'ldlinux.sys' on the Flash device, making it bootable. Note: you may see your device disappear and reappear on your desktop a few times as the script is running - this is normal. 5. When the script completes, close the terminal window and Eject the device. Your USB Flash device is now ready to boot into unRAID Server OS. Quote Link to comment
fiscalcon Posted September 12, 2014 Share Posted September 12, 2014 Thanks! Installing now. Quote Link to comment
JM2005 Posted September 12, 2014 Share Posted September 12, 2014 Thank you Tom and your team! Quote Link to comment
sacretagent Posted September 12, 2014 Share Posted September 12, 2014 automated update in extensions not ready yet ? just asking tried to click check update but nothing found Quote Link to comment
limetech Posted September 12, 2014 Author Share Posted September 12, 2014 automated update in extensions not ready yet ? just asking tried to click check update but nothing found The next release will use that. The automated update creates a folder on the flash and moves all the "current" release files in there: bzimage, bzroot, etc. It then copies the "new" release files to the flash. I didn't want any -beta7/8 releases left around in case by mistake someone runs them, so for this release, sorry manual method. Quote Link to comment
Squid Posted September 12, 2014 Share Posted September 12, 2014 Also, maybe its just me, but I also have lost the ability to add docker containers via templates. The drop down menu just states "Select a Template". If I revert back to beta 8, all the templates are there, but they disappeared from my beta9 But, all of the containers which I was running before are still running. Quote Link to comment
gfjardim Posted September 12, 2014 Share Posted September 12, 2014 Also, maybe its just me, but I also have lost the ability to add docker containers via templates. The drop down menu just states "Select a Template". If I revert back to beta 8, all the templates are there, but they disappeared from my beta9 But, all of the containers which I was running before are still running. Sorry for that. We changed the user templates back to the flash drive: BETA 8 BETA 9 /var/lib/docker/unraid-templates /boot/config/plugins/dockerMan/templates-user cp -rf /var/lib/docker/unraid-templates/* /boot/config/plugins/dockerMan/templates-user/ While LT don't create their own containers, you can use several of community ones using the templates below. [glow=red,2,300]UPDATE:[/glow] To help the transition, I've created a template repository here: https://github.com/gfjardim/docker-containers/tree/templates After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save. Quote Link to comment
BRiT Posted September 12, 2014 Share Posted September 12, 2014 I've looked at both directories for docker templates and they are all empty. root@REAVER:~# ls -al /boot/config/plugins/dockerMan/ total 128 drwxrwxrwx 4 root root 32768 Sep 11 23:46 ./ drwxrwxrwx 5 root root 32768 Sep 11 23:46 ../ drwxrwxrwx 2 root root 32768 Sep 11 23:46 templates/ drwxrwxrwx 2 root root 32768 Sep 11 23:46 templates-user/ root@REAVER:~# ls -al /boot/config/plugins/dockerMan/templates-user/ total 64 drwxrwxrwx 2 root root 32768 Sep 11 23:46 ./ drwxrwxrwx 4 root root 32768 Sep 11 23:46 ../ root@REAVER:~# ls -al /boot/config/plugins/dockerMan/templates templates/ templates-user/ root@REAVER:~# ls -al /boot/config/plugins/dockerMan/templates total 64 drwxrwxrwx 2 root root 32768 Sep 11 23:46 ./ drwxrwxrwx 4 root root 32768 Sep 11 23:46 ../ root@REAVER:~# ls -al /var/lib/docker/unraid-templates/ total 16 drwxrwxrwx 1 root root 0 Sep 8 23:02 ./ drwxr-xr-x 1 root root 180 Sep 8 23:02 ../ Quote Link to comment
gfjardim Posted September 12, 2014 Share Posted September 12, 2014 I've looked at both directories for docker templates and they are all empty. root@REAVER:~# ls -al /boot/config/plugins/dockerMan/ total 128 drwxrwxrwx 4 root root 32768 Sep 11 23:46 ./ drwxrwxrwx 5 root root 32768 Sep 11 23:46 ../ drwxrwxrwx 2 root root 32768 Sep 11 23:46 templates/ drwxrwxrwx 2 root root 32768 Sep 11 23:46 templates-user/ root@REAVER:~# ls -al /boot/config/plugins/dockerMan/templates-user/ total 64 drwxrwxrwx 2 root root 32768 Sep 11 23:46 ./ drwxrwxrwx 4 root root 32768 Sep 11 23:46 ../ root@REAVER:~# ls -al /boot/config/plugins/dockerMan/templates templates/ templates-user/ root@REAVER:~# ls -al /boot/config/plugins/dockerMan/templates total 64 drwxrwxrwx 2 root root 32768 Sep 11 23:46 ./ drwxrwxrwx 4 root root 32768 Sep 11 23:46 ../ root@REAVER:~# ls -al /var/lib/docker/unraid-templates/ total 16 drwxrwxrwx 1 root root 0 Sep 8 23:02 ./ drwxr-xr-x 1 root root 180 Sep 8 23:02 ../ The /boot/config/plugins/dockerMan/templates directory will we filled with templates from repositories; the /boot/config/plugins/dockerMan/templates-user will store the user defined templates, those famous my-*.xml Quote Link to comment
Squid Posted September 12, 2014 Share Posted September 12, 2014 Also, maybe its just me, but I also have lost the ability to add docker containers via templates. The drop down menu just states "Select a Template". If I revert back to beta 8, all the templates are there, but they disappeared from my beta9 But, all of the containers which I was running before are still running. Sorry for that. We changed the user templates back to the flash drive: BETA 8 BETA 9 /var/lib/docker/unraid-templates /boot/config/plugins/dockerMan/templates-user While LT don't create their own containers, you can use several of community ones using the templates below. [glow=red,2,300]UPDATE:[/glow] To help the transition, I've created a template repository here: https://github.com/gfjardim/docker-containers/tree/templates After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save. Works awesome! You the man! Quote Link to comment
BRiT Posted September 12, 2014 Share Posted September 12, 2014 So how exactly do we get those updated? Do we have to wait for yet another update to do so? Or do we have to manually update the docker extension? Quote Link to comment
jakea333 Posted September 12, 2014 Share Posted September 12, 2014 Just to clarify for everyone. To get the templates back, you need to this first: [glow=red,2,300]UPDATE:[/glow] To help the transition, I've created a template repository here: https://github.com/gfjardim/docker-containers/tree/templates After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save. Then, copy the my-* templates to the new directory on the flash drive. Something like: cp /var/lib/docker/unraid-templates/* /boot/config/plugins/dockerMan/templates-user/ Correct me if I'm wrong. Quote Link to comment
Manticore Posted September 12, 2014 Share Posted September 12, 2014 5am here in Ireland. Time to take a break from playing Destiny and apply the update. Thanks for all the hard work guys Quote Link to comment
BRiT Posted September 12, 2014 Share Posted September 12, 2014 Just to clarify for everyone. To get the templates back, you need to this first: [glow=red,2,300]UPDATE:[/glow] To help the transition, I've created a template repository here: https://github.com/gfjardim/docker-containers/tree/templates After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save. Then, copy the my-* templates to the new directory on the flash drive. Something like: cp /var/lib/docker/unraid-templates/* /boot/config/plugins/dockerMan/templates-user/ Correct me if I'm wrong. There are no my-* files contained in https://github.com/gfjardim/docker-containers/tree/templates . So something isn't right in the supposed steps you listed. Quote Link to comment
stewartwb Posted September 12, 2014 Share Posted September 12, 2014 Maybe its just a stupid question, but I see that when the array is stopped that I now have the option to change the number of slots... Why would I ever want to do that? That feature was added in 6.0 beta 7. Use it to create a BTRFS cache pool with multiple drives for fault tolerance. Older versions only allowed a single cache drive, but now you can have multiple drives in a cache pool. Quote Link to comment
jakea333 Posted September 12, 2014 Share Posted September 12, 2014 Just to clarify for everyone. To get the templates back, you need to this first: [glow=red,2,300]UPDATE:[/glow] To help the transition, I've created a template repository here: https://github.com/gfjardim/docker-containers/tree/templates After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save. Then, copy the my-* templates to the new directory on the flash drive. Something like: cp /var/lib/docker/unraid-templates/* /boot/config/plugins/dockerMan/templates-user/ Correct me if I'm wrong. There are no my-* files contained in https://github.com/gfjardim/docker-containers/tree/templates . So something isn't right in the supposed steps you listed. Check the location I'm copying from. That's from the docker image. Your my-* templates are stored locally, not in his repo. Quote Link to comment
BillyJ Posted September 12, 2014 Share Posted September 12, 2014 To get my docker templates back i simply clicked on the Name of each app in the Docker manager and clicked add again. It then recreated the templates correctly on the flash drive. Quote Link to comment
Squid Posted September 12, 2014 Share Posted September 12, 2014 To get my docker templates back i simply clicked on the Name of each app in the Docker manager and clicked add again. It then recreated the templates correctly on the flash drive. All I did was copy them from /var/lib/docker/unraid-templates to /boot/config/plugins/dockerMan/templates-user like gfjardim said Quote Link to comment
bonzi Posted September 12, 2014 Share Posted September 12, 2014 I'm gonna stay on beta 6 for awhile till this reiserfs stuff calms down and the patch makes its way into the kernel hopefully with some rigorous testing.. Quote Link to comment
lars Posted September 12, 2014 Share Posted September 12, 2014 Also, maybe its just me, but I also have lost the ability to add docker containers via templates. The drop down menu just states "Select a Template". If I revert back to beta 8, all the templates are there, but they disappeared from my beta9 But, all of the containers which I was running before are still running. same here - not that i really care, but yes, not working here as well. Quote Link to comment
peter_sm Posted September 12, 2014 Share Posted September 12, 2014 @LT What is the safest/best format to transfer to? BTRFS or XFS? or maybe wait for EXT4? I know that are discussion on several places about this. But I need your opinion on this. BR Peter Quote Link to comment
Owel Posted September 12, 2014 Share Posted September 12, 2014 Hi, Currently I'm on beta 7, want to update to 9. Are there any Docker related task to do? like it was from 7 to 8? Regards Owel Quote Link to comment
jbartlett Posted September 12, 2014 Share Posted September 12, 2014 Hi, Currently I'm on beta 7, want to update to 9. Are there any Docker related task to do? like it was from 7 to 8? Regards Owel Follow the instructions from beta 7 to beta 8, they'll be the same for beta 9. Quote Link to comment
binhex Posted September 12, 2014 Share Posted September 12, 2014 hi gfjardim, quick question for you regards this, i see beta 8 onwards now includes your plugin in stock unraid, so my question is moving from beta 7 straight to beta 9 do i delete docker plugin files located on the flash drive or not?, i see that your now reverting back to having the docker templates located on the flash drive, so im guessing i need to leave the folder /boot/config/plugins/DockerMan alone and not delete it, yes?, reason i ask is that in beta 8 release notes from tom he stated that its safe to delete /boot/config/plugins/Docker from your flash drive, just wondered if this is still true or not?, just trying to reduce the amount of redundant files on my flash drive. Also, maybe its just me, but I also have lost the ability to add docker containers via templates. The drop down menu just states "Select a Template". If I revert back to beta 8, all the templates are there, but they disappeared from my beta9 But, all of the containers which I was running before are still running. Sorry for that. We changed the user templates back to the flash drive: BETA 8 BETA 9 /var/lib/docker/unraid-templates /boot/config/plugins/dockerMan/templates-user While LT don't create their own containers, you can use several of community ones using the templates below. [glow=red,2,300]UPDATE:[/glow] To help the transition, I've created a template repository here: https://github.com/gfjardim/docker-containers/tree/templates After update the plugin, a new field will appear on the Docker extension page. Add this address there and click Save. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.