April 21, 201511 yr you have to click update container rather than edit. Yeah i tried that and its not go, i guess it just foobar, i will just start a new container and delete this one. no biggie deleted the container and pull it with all new data and still it fails at this part After this operation, 22.5 MB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main rsync amd64 3.1.0-2ubuntu0.1 [283 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty/main liberror-perl all 0.17-1.1 [21.1 kB] Get:3 http://archive.ubuntu.com/ubuntu/ trusty/main git-man all 1:1.9.1-1 [698 kB] Get:4 http://archive.ubuntu.com/ubuntu/ trusty/main git amd64 1:1.9.1-1 [2555 kB] Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main patch amd64 2.7.1-4ubuntu1 404 Not Found [iP: 91.189.91.15 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/patch/patch_2.7.1-4ubuntu1_amd64.deb 404 Not Found [iP: 91.189.91.15 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Fetched 3557 kB in 5s (627 kB/s) /etc/my_init.d/edge.sh: line 9: git: command not found chown: cannot access '/opt/sickrage': No such file or directory *** /etc/my_init.d/edge.sh failed with status 1 *** Killing all processes... When i paste the address http://archive.ubuntu.com/ubuntu/pool/main/p/patch/patch_2.7.1-4ubuntu1_amd64.deb givesme the 404 error so I went to the parent directory and i can see where its looking for patch_2.7.1-4ubuntu1_amd64.deb and its not there. whats there is (see attachment) Other than rebooting the unraid server im not sure hot to force the update.
April 21, 201511 yr did you delete the container and image or just the container, try deleting the image if it was just the container. drop out to the unraid command prompt and paste the output of docker ps -a
April 21, 201511 yr did you delete the container and image or just the container, try deleting the image if it was just the container. drop out to the unraid command prompt and paste the output of docker ps -a both but i will try again
April 21, 201511 yr did you delete the container and image or just the container, try deleting the image if it was just the container. drop out to the unraid command prompt and paste the output of docker ps -a both but i will try again login as: root [email protected]'s password: Last login: Sun Apr 19 22:12:04 2015 from 10.0.1.124 Linux 3.18.5-unRAID. root@LahomaMediaCenter:~# docker ps -a CONTAINER ID IMAGE COMMAND CRE ATED STATUS PORTS NAMES 8678404b2314 needo/couchpotato:latest "/sbin/my_init" 23 hours ago Up 23 hours 0.0.0.0:5050->5050/tcp CouchPotato 3f4c1bff91b5 needo/sabnzbd:latest "/sbin/my_init" 23 hours ago Up 23 hours 0.0.0.0:8080->8080/tcp SABnzbd b3633f8f338e mediabrowser/mbserver:latest "/start.sh mediabrow 36 hours ago Up 36 hours 7359/udp, 1900/udp, 0.0.0.0:1900->1900/tcp, 0.0.0.0:7359->7359/tcp, 0.0.0.0:8096->8096/tcp, 0.0.0.0:8920->8920/tcp MediaBrowser 46d1c240f938 gfjardim/owncloud:latest "/sbin/my_init" 36 hours ago Up 36 hours 8001/tcp, 0.0.0.0:8000->8000/tcp ownCloud 45883fee2fcc captinsano/foldingathome:latest "/sbin/my_init" 2 w eeks ago Up 2 weeks 0.0.0.0:7396->7396/tcp, 0.0.0.0:36330->3633 0/tcp FoldingAtHome root@LahomaMediaCenter:~# ^C root@LahomaMediaCenter:~# Not the best formating but as you can see no SickRage
April 21, 201511 yr this is really embarassing and i will put in another pull request and get an opticians appt too. i updated sickbeard and you have sickrage, i'm working on another container at the moment and will look at this one later or tommorow and put in a pull request to needo for it.
April 21, 201511 yr this is really embarassing and i will put in another pull request and get an opticians appt too. i updated sickbeard and you have sickrage, i'm working on another container at the moment and will look at this one later or tommorow and put in a pull request to needo for it. awesome, thanks, where the donate button, i'll buy you a beer
April 21, 201511 yr this is really embarassing and i will put in another pull request and get an opticians appt too. i updated sickbeard and you have sickrage, i'm working on another container at the moment and will look at this one later or tommorow and put in a pull request to needo for it. awesome, thanks, where the donate button, i'll buy you a beer i made the changes, needo merged it and it's building now on dockerhub.
April 21, 201511 yr I seem to be having issues with the needo sickrage container not understanding the "EDGE=1" switch. When I restart the container it falls back 215 odd commits. Normally that's not a big issue but the problem is the database has now incremented from 40 to 41 so it takes a bit of fiddling, copying and screwing around to get sickrage alive again. If this is no longer being updated, is there another sickrage container people are using ? It has been broken for a bit. I finally fixed it and pushed it to docker so I could use it myself. You are welcome to pull from it if you want. It's just the same as Needo's docker, but with a fixed EDGE file. https://hub.docker.com/u/ninthwalker/ docker command: docker run -d --name="sickrage" -v /path/to/sickrage/data:/config -v /path/to/downloads:/downloads -v /path/to/tv:/tv -v /etc/localtime:/etc/localtime:ro -e EDGE=1 -p 8081:8081 ninthwalker/brentrage nw, your container come up as needing an update. I ran it and now it's broken. Here's the log. Any ideas ? *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/edge.sh... Reading package lists... Building dependency tree... Reading state information... The following extra packages will be installed: git-man liberror-perl patch rsync Suggested packages: gettext-base git-daemon-run git-daemon-sysvinit git-doc git-el git-email git-gui gitk gitweb git-arch git-bzr git-cvs git-mediawiki git-svn ed diffutils-doc The following NEW packages will be installed: git git-man liberror-perl patch rsync 0 upgraded, 5 newly installed, 0 to remove and 49 not upgraded. Need to get 84.4 kB/3642 kB of archives. After this operation, 22.5 MB of additional disk space will be used. Err http://archive.ubuntu.com/ubuntu/ trusty-updates/main patch amd64 2.7.1-4ubuntu1 404 Not Found [iP: 91.189.92.200 80] E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/p/patch/patch_2.7.1-4ubuntu1_amd64.deb 404 Not Found [iP: 91.189.92.200 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? /etc/my_init.d/edge.sh: line 9: git: command not found chown: cannot access '/opt/sickrage': No such file or directory *** /etc/my_init.d/edge.sh failed with status 1 *** Killing all processes...
April 27, 201511 yr needo - I've noticed that some of your containers use phusion/baseimage:0.9.15 and others phusion/baseimage:0.9.16 Are you in the process of updating all of them, and is there any reason to not use "latest" so you dont have to modify to docker file whenever a new phusion release is put out?
April 29, 201511 yr I just upgraded to 6.0 and am still getting the hang of Docker. I installed a few of your containers and I'm getting something strange with mariadb. After one of the settings updates to the container config in unraid, I now see some additional containers with the mariadb icon next to them (none running). They are all from the needo/mariadb:latest repo and sound like Ubuntu releases the container names are desperate_feynman, drunk_colden, focused_engelbart. Is it safe to delete them or is there some kind of dependency?
April 29, 201511 yr I'm using the SABnzb container and it seems that whatever I configure the listening port number for SAB to it will revert to 8080 when the container is restarted. I realize this isnt't a huge deal because the port can be mapped in the config, but the other containers of your I'm using don't do that.
April 29, 201511 yr I just upgraded to 6.0 and am still getting the hang of Docker. I installed a few of your containers and I'm getting something strange with mariadb. After one of the settings updates to the container config in unraid, I now see some additional containers with the mariadb icon next to them (none running). They are all from the needo/mariadb:latest repo and sound like Ubuntu releases the container names are desperate_feynman, drunk_colden, focused_engelbart. Is it safe to delete them or is there some kind of dependency? Not sure how you got those, but if the docker command does not specify a name, then one is randomly assigned. Definitely not normal if you are doing everything from the docker manager in unRAID. You should delete them and if they won't delete find out what else is using them and delete those too. If you want a docker to use a different port you should specify it in the port mappings. For example, docker port 8080 = host port whatever.
April 29, 201511 yr I just upgraded to 6.0 and am still getting the hang of Docker. I installed a few of your containers and I'm getting something strange with mariadb. After one of the settings updates to the container config in unraid, I now see some additional containers with the mariadb icon next to them (none running). They are all from the needo/mariadb:latest repo and sound like Ubuntu releases the container names are desperate_feynman, drunk_colden, focused_engelbart. Is it safe to delete them or is there some kind of dependency? are you adding containers from the command line ?
April 29, 201511 yr I just upgraded to 6.0 and am still getting the hang of Docker. I installed a few of your containers and I'm getting something strange with mariadb. After one of the settings updates to the container config in unraid, I now see some additional containers with the mariadb icon next to them (none running). They are all from the needo/mariadb:latest repo and sound like Ubuntu releases the container names are desperate_feynman, drunk_colden, focused_engelbart. Is it safe to delete them or is there some kind of dependency? are you adding containers from the command line ? No, not at all. The only docker command line tools I've users are ps and exec (needed a shell to check a file in the container).
April 29, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified)
April 29, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect.
April 29, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect. docker ps -a
April 29, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect. docker ps -a That command showed them all and I was able to remove the ones I didn't want with no apparent ill-effect. I THINK what may have caused them to be created was running docker run <param> uname -a where I was probably using an incorrect value for param and that caused the containers to be created. In fact (just tried it) if I run docker run "needo/sabnzbd:latest" uname -a it will create an un-named copy.
April 29, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect. docker ps -a That command showed them all and I was able to remove the ones I didn't want with no apparent ill-effect. I THINK what may have caused them to be created was running docker run <param> uname -a where I was probably using an incorrect value for param and that caused the containers to be created. In fact (just tried it) if I run docker run "needo/sabnzbd:latest" uname -a it will create an un-named copy. Yes it will. To avoid this, you have to add a "--rm=true" argument.
April 29, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect. docker ps -a That command showed them all and I was able to remove the ones I didn't want with no apparent ill-effect. I THINK what may have caused them to be created was running docker run <param> uname -a where I was probably using an incorrect value for param and that caused the containers to be created. In fact (just tried it) if I run docker run "needo/sabnzbd:latest" uname -a it will create an un-named copy. lol, i thought you was doing something at the command line.
April 30, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect. docker ps -a That command showed them all and I was able to remove the ones I didn't want with no apparent ill-effect. I THINK what may have caused them to be created was running docker run <param> uname -a where I was probably using an incorrect value for param and that caused the containers to be created. In fact (just tried it) if I run docker run "needo/sabnzbd:latest" uname -a it will create an un-named copy. lol, i thought you was doing something at the command line. Yes, but being new to docker I'm sure you could understand that attempting to run a command on an invalid container (my definition being one that I don't currently have installed) resulting in the creation of a container is a surprise. I'm sure it's very clearly documented but none the less a surprise. I'll be more careful in the future.
April 30, 201511 yr then it's unusual for you to have unnamed containers (the weird names are assigned by docker when there is no name specified) How does the unraid docker page get a list of containers? If I run "docker images" I only get the 4 containers I expect. docker ps -a That command showed them all and I was able to remove the ones I didn't want with no apparent ill-effect. I THINK what may have caused them to be created was running docker run <param> uname -a where I was probably using an incorrect value for param and that caused the containers to be created. In fact (just tried it) if I run docker run "needo/sabnzbd:latest" uname -a it will create an un-named copy. lol, i thought you was doing something at the command line. Yes, but being new to docker I'm sure you could understand that attempting to run a command on an invalid container (my definition being one that I don't currently have installed) resulting in the creation of a container is a surprise. I'm sure it's very clearly documented but none the less a surprise. I'll be more careful in the future. tell me about it, lol. did it myself a few times.
April 30, 201511 yr recently my plex docker started having a lot of issues and was wondering anyone elses thoughts? all other dockers seem to be fine as well as my network. also plex logs dont show any timeout issues. it does eventually come back but when it does it seems to only last for an hour or so until shows start stuttering and the like. i am on 6b15 and latest plexpass version. connect: Connection timed out *** Shutting down runit daemon (PID 180)... *** Killing all processes... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/firstrun.sh... Version not changed - 0.9.11.17.986-269b82b *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 17 6 3000 /config/Library/Application Support unlimited connect: Connection timed out
April 30, 201511 yr I just upgraded to Unraid v6 and I am starting to work with Docker. I installed the Sickrage Docker and it looks to be running fine, but I can not login to the webui. Originally the Sickrage config was set to use web_host = 192.168.0.100 but that would give me errors, so I switched it to: web_host = localhost That no longer gave errors, but I can not connect to the webUI at all. I thought it would pass-through to my servers local ip of 192.168.0.100. I changed from bridged mode to host, and that works. What could be the issue in bridge mode?
April 30, 201511 yr A little more to the connection timeouts I am also getting this prior to it finally coming online, any thoughts? Entity: line 6: parser error : Opening and ending tag mismatch: hr line 5 and body ^ Entity: line 7: parser error : Opening and ending tag mismatch: body line 3 and html ^ Entity: line 8: parser error : Premature end of data in tag html line 1 ^ Entity: line 6: parser error : Opening and ending tag mismatch: hr line 5 and body ^ Entity: line 7: parser error : Opening and ending tag mismatch: body line 3 and html ^ Entity: line 8: parser error : Premature end of data in tag html line 1 ^ connect: Connection timed out
Archived
This topic is now archived and is closed to further replies.