msimard8

Members
  • Posts

    12
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

msimard8's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Copied from smdions thread. I am still having problems and have no idea how to debug this: Capt, having issues with your ddclient docker run -d --name="ddclient" --net="host" -e TZ="America/New_York" -v "/mnt/user/docker/volume_data/ddclient":"/config":rw captinsano/ddclient I get this on loop: Starting DDClient WARNING: unable to determine IP address My config protocol=namecheap use=web, web=checkip.dyndns.com/, web-skip='IP Address' server=dynamicdns.park-your-domain.com login=**.com password=67bea0***** test Running unraid 6.0-beta10a (if that matters) EDIT: The config works (verified on separate linux box). It just not working in the container.
  2. Capt, having issues with your ddclient docker run -d --name="ddclient" --net="host" -e TZ="America/New_York" -v "/mnt/user/docker/volume_data/ddclient":"/config":rw captinsano/ddclient I get this on loop: Starting DDClient WARNING: unable to determine IP address My config protocol=namecheap use=web, web=checkip.dyndns.com/, web-skip='IP Address' server=dynamicdns.park-your-domain.com login=**.com password=67bea0***** test Running unraid 6.0-beta10a (if that matters)
  3. Having issues again with my new images. Everything was running fine.. Getting this response from all of my dockers. If I stop and restart them: root@localhost:# /usr/bin/docker run -d --name="duck-dns" --net="bridge" -e TZ="America/New_York" -v "/mnt/disk1/docker/volume_data/duckdns/":"/config":rw coppit/duckdns 2014/11/26 00:44:14 Error response from daemon: unexpected end of JSON input Very similar to yesterday This is starting to become more trouble than its worth. Could i be running low on disk space? If so how do I check? How do I grow it? I currently have a 10 GB docker image
  4. I managed to get docker working. This is what I did. - Rename the current docker image. - Reboot unraid - The new docker was created successfully. So something i noticed, when I tried to stop the array, the logs indicated that docker would not die, then the array wouldn't unmount. The docker daemon also wasn't running according to ps and docker itself. As a result I would have to force reboot. So for some reason when docker would try to boot up, it would be put into a bad state that it couldn't get out of. As a result, the gui/CLI would fail when trying to create a new image Thanks for the help
  5. Just tried it. No luck. The USB did need a repair though. I also tried reformatting and putting the files back on it. Still no luck.
  6. here is the output of /var/docker.log 2014/11/24 22:12:37 docker daemon: 1.2.0 7649264eb89614ddaed331560622ea0eb92c299c; execdriver: native; graphdriver: btrfs [d732babd] +job serveapi(unix:///var/run/docker.sock) [info] Listening for HTTP on unix (/var/run/docker.sock) 2014/11/24 22:12:42 Couldn't create Tag store: unexpected end of JSON input 2014/11/24 22:13:10 docker daemon: 1.2.0 7649264eb89614ddaed331560622ea0eb92c299c; execdriver: native; graphdriver: btrfs [b6d75ac5] +job serveapi(unix:///var/run/docker.sock) 2014/11/24 22:13:10 Couldn't create Tag store: unexpected end of JSON input
  7. No luck. Renamed docker image. Same result. Nov 24 22:02:12 Vader php: /etc/rc.d/rc.docker start Nov 24 22:02:12 Vader php: starting docker ... Nov 24 22:02:22 Vader php: Didn't even create a new docker image in the directory. This is interesting.
  8. I installed unRaid a couple weeks ago, and all has been well. Had several dockers working fine. Then today I had a power failure (lots of high winds) and now I can not get docker to start. Syslog show Nov 24 20:27:08 Vader php: /etc/rc.d/rc.docker start Nov 24 20:27:08 Vader php: starting docker ... Nov 24 20:27:19 Vader php: and thats it. Launching from the command line doesn't seem to give me any more info. Docker is definitely not running. If I run... root@Vader:/mnt# docker images 2014/11/24 20:36:54 Cannot connect to the Docker daemon. Is 'docker -d' running on this host? root@Vader:/mnt# ps -aux | grep docker Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html root 4801 0.0 0.0 5096 1756 pts/1 S+ 20:36 0:00 grep docker Anything I can do to debug this? Any ideas on what it could be? Thanks, Michael
  9. My unRAID server just booted after following those steps. Thank you.
  10. Did you ever get this fixed. I am having the same issue.