kode54 Posted December 12, 2016 Share Posted December 12, 2016 Try deleting network.cfg, reboot, and reconfigure your network changes from scratch? Fixed my Docker issues from downgrading, may fix your Samba issues from upgrading. Maybe also keep a backup copy, see how the two differ between your original and the recreated version. Quote Link to comment
dikkiedirk Posted December 18, 2016 Share Posted December 18, 2016 I had access problems to my server on a Windows 10 machine. I set my routers DHCP server to reserve an IP for the server and rebooted the server. My Windows 10 machine can now access the server again. I also enabled NETBIOS on ipv4 on the Windows 10 machine. My Dune mediaplayer still can't access my server by name only by IP address. Quote Link to comment
dtempleton Posted December 20, 2016 Share Posted December 20, 2016 Only partial joy here. Tried to update from 6.0 (have been out of the country) using the update button on the plugins page, then pushing the 'reboot' button in the webGUI. Failed to start in 45 minutes. Docker process seems to be running but not working (syslog attached shows a hang in docker start). All of this is in the syslog (fourth). A series of restarts always yielded a stable situation in which Docker would not stay open. I suspect that the issue is that my docker.img is 32 gb when there is reference in the syslog to 'max' being 30. A rebuilt (and empty) docker.img is 30 GB, see below. Finally, I renamed my docker.img and rebooted with no mountable image. Docker starts, but the tab in the webGUI is obviously empty. An unpopulated docker.img is created where the old one was. Now I'm facing rebuilding my docker. Most of the containers I can just re-download but a couple are those I have modified. I have backups of everything, but am unsure where I can access those changed containers. For example I modified a Handbrake container to auto-start some scripts to transcode files automatically. I have the scripts, but can't recall which handbrake I used and what start scripts were modified. Your advice will be appreciated Fourth_syslog.txt Quote Link to comment
darkside40 Posted December 21, 2016 Share Posted December 21, 2016 Facing the same problem here. Just upgraded from 6.1.9 to 6.2.4. Docker always stays at Stopped. My Docker Image is just 10GB. Here is what syslog says: Dec 21 15:05:01 HTMS emhttp: shcmd (1837): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 10 |& logger Dec 21 15:05:01 HTMS kernel: BTRFS info (device loop0): disk space caching is enabled Dec 21 15:05:01 HTMS kernel: BTRFS: has skinny extents Dec 21 15:05:01 HTMS root: Resize '/var/lib/docker' of 'max' Dec 21 15:05:01 HTMS kernel: BTRFS info (device loop0): new size for /dev/loop0 is 10737418240 Dec 21 15:05:01 HTMS emhttp: shcmd (1839): /etc/rc.d/rc.docker start |& logger Dec 21 15:05:01 HTMS root: starting docker ... Dec 21 15:05:02 HTMS emhttp: shcmd (1841): umount /var/lib/docker |& logger How can i get my Dockers back? Quote Link to comment
Frank1940 Posted December 21, 2016 Share Posted December 21, 2016 Facing the same problem here. Just upgraded from 6.1.9 to 6.2.4. Docker always stays at Stopped. My Docker Image is just 10GB. Here is what syslog says: Dec 21 15:05:01 HTMS emhttp: shcmd (1837): set -o pipefail ; /usr/local/sbin/mount_image '/mnt/cache/docker.img' /var/lib/docker 10 |& logger Dec 21 15:05:01 HTMS kernel: BTRFS info (device loop0): disk space caching is enabled Dec 21 15:05:01 HTMS kernel: BTRFS: has skinny extents Dec 21 15:05:01 HTMS root: Resize '/var/lib/docker' of 'max' Dec 21 15:05:01 HTMS kernel: BTRFS info (device loop0): new size for /dev/loop0 is 10737418240 Dec 21 15:05:01 HTMS emhttp: shcmd (1839): /etc/rc.d/rc.docker start |& logger Dec 21 15:05:01 HTMS root: starting docker ... Dec 21 15:05:02 HTMS emhttp: shcmd (1841): umount /var/lib/docker |& logger How can i get my Dockers back? Did you read the first two posts in this thread: http://lime-technology.com/forum/index.php?topic=51874.0 Quote Link to comment
darkside40 Posted December 21, 2016 Share Posted December 21, 2016 Deleted the docker.img was the fastest solution. Quote Link to comment
dtempleton Posted December 21, 2016 Share Posted December 21, 2016 Yes, deleting the docker.img was the fastest solution, but it's still not clear what was wrong with the previous docker.img . mine was on my cache drive, not an unassigned device. I did take the opportunity to clean up my docker install by editing the run command. A tidy solution to get scripts stored off the image is to include the command: --entrypoint=\"/container/path/script.sh\" command. I doubt that the quotes need to be escaped. 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.