October 24, 201411 yr I noticed some request for a beets container. I created one here long time ago now: https://github.com/HurricaneHernandez/docker-beets If you want some edits or modifications please let me know and I will try and accommodate the changes or requests as best I can. This image will receive an update once the new beta for unRAID is released.
October 24, 201411 yr I am curious why you chose "FROM ubuntu:saucy". Almost every other container here currently uses phusion so downloding a whole new base OS layer may discourage uNRAID users (as in will Good work though this is definitely an app people should have
October 24, 201411 yr Author I will update to trusty. Phusion uses trusty so that will resolve the issue of downloading a whole new base image. I don't believe in using phusion's image for beets because it is overkill. Beets in usually done in batch run's and with docker 1.3 the exec command will make the sshd service on the container useless and will be remove. Everything else phusion's image address is not applicable for something like beets.
October 24, 201411 yr I would tend to agree. Worth noting that the proposed unRAID docker base image is 14.04.x so it sounds like a perfect match. docker exec is a game changer so roll on unRAID b11 Nice work I will try this over the weekend. Kudos
November 19, 201411 yr @hurrircanehernadez Great work! Any luck porting this to a trusty docker? Is it possible to add beets to your template repo?
December 21, 201411 yr Any update on this docker... I really would like to test beets on my collection which is very disorganized.
December 22, 201411 yr I'm also waiting patiently! Hurricane has been quite so, I've moved this over to phusion and have it automatically download the beets.sh and put it in the config folder. I do not use Beets so it is in my beta repository right now until we are sure it works with the migration to phusion. Please test and let me know in this thread. NOTE: All credit for this goes to Hurricane.. I made some simple changes Beta Repo: https://github.com/smdion/docker-containers/tree/beta-templates
December 23, 201411 yr Ive installed it, however cannot get it to start. This is whats in my log Dec 23 14:40:30 SERVO php: /usr/bin/docker start Beets Dec 23 14:40:30 SERVO kernel: device vetha4c60a0 entered promiscuous mode Dec 23 14:40:30 SERVO avahi-daemon[2065]: Withdrawing workstation service for veth679e541. Dec 23 14:40:30 SERVO kernel: eth0: renamed from veth679e541 Dec 23 14:40:30 SERVO php: Beets Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO php: Dec 23 14:40:31 SERVO avahi-daemon[2065]: Withdrawing workstation service for vetha4c60a0. Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Dec 23 14:40:31 SERVO kernel: device vetha4c60a0 left promiscuous mode Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state
December 23, 201411 yr Ive installed it, however cannot get it to start. This is whats in my log Dec 23 14:40:30 SERVO php: /usr/bin/docker start Beets Dec 23 14:40:30 SERVO kernel: device vetha4c60a0 entered promiscuous mode Dec 23 14:40:30 SERVO avahi-daemon[2065]: Withdrawing workstation service for veth679e541. Dec 23 14:40:30 SERVO kernel: eth0: renamed from veth679e541 Dec 23 14:40:30 SERVO php: Beets Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO php: Dec 23 14:40:31 SERVO avahi-daemon[2065]: Withdrawing workstation service for vetha4c60a0. Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Dec 23 14:40:31 SERVO kernel: device vetha4c60a0 left promiscuous mode Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Sorry, I'm a newb when it comes to Beets. Are you saying the docker itself won't start or the Beets app?
December 23, 201411 yr Ive installed it, however cannot get it to start. This is whats in my log Dec 23 14:40:30 SERVO php: /usr/bin/docker start Beets Dec 23 14:40:30 SERVO kernel: device vetha4c60a0 entered promiscuous mode Dec 23 14:40:30 SERVO avahi-daemon[2065]: Withdrawing workstation service for veth679e541. Dec 23 14:40:30 SERVO kernel: eth0: renamed from veth679e541 Dec 23 14:40:30 SERVO php: Beets Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO php: Dec 23 14:40:31 SERVO avahi-daemon[2065]: Withdrawing workstation service for vetha4c60a0. Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Dec 23 14:40:31 SERVO kernel: device vetha4c60a0 left promiscuous mode Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Sorry, I'm a newb when it comes to Beets. Are you saying the docker itself won't start or the Beets app? All good, so am I The docker itself wont start, when i click start it it produces the above in the log and fails to start
December 26, 201411 yr Ive installed it, however cannot get it to start. This is whats in my log Dec 23 14:40:30 SERVO php: /usr/bin/docker start Beets Dec 23 14:40:30 SERVO kernel: device vetha4c60a0 entered promiscuous mode Dec 23 14:40:30 SERVO avahi-daemon[2065]: Withdrawing workstation service for veth679e541. Dec 23 14:40:30 SERVO kernel: eth0: renamed from veth679e541 Dec 23 14:40:30 SERVO php: Beets Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO php: Dec 23 14:40:31 SERVO avahi-daemon[2065]: Withdrawing workstation service for vetha4c60a0. Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Dec 23 14:40:31 SERVO kernel: device vetha4c60a0 left promiscuous mode Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Sorry, I'm a newb when it comes to Beets. Are you saying the docker itself won't start or the Beets app? All good, so am I The docker itself wont start, when i click start it it produces the above in the log and fails to start Back from Christmas Holiday... I'll take a look today
December 27, 201411 yr Ive installed it, however cannot get it to start. This is whats in my log Dec 23 14:40:30 SERVO php: /usr/bin/docker start Beets Dec 23 14:40:30 SERVO kernel: device vetha4c60a0 entered promiscuous mode Dec 23 14:40:30 SERVO avahi-daemon[2065]: Withdrawing workstation service for veth679e541. Dec 23 14:40:30 SERVO kernel: eth0: renamed from veth679e541 Dec 23 14:40:30 SERVO php: Beets Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO kernel: docker0: port 3(vetha4c60a0) entered forwarding state Dec 23 14:40:30 SERVO php: Dec 23 14:40:31 SERVO avahi-daemon[2065]: Withdrawing workstation service for vetha4c60a0. Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Dec 23 14:40:31 SERVO kernel: device vetha4c60a0 left promiscuous mode Dec 23 14:40:31 SERVO kernel: docker0: port 3(vetha4c60a0) entered disabled state Sorry, I'm a newb when it comes to Beets. Are you saying the docker itself won't start or the Beets app? All good, so am I The docker itself wont start, when i click start it it produces the above in the log and fails to start Back from Christmas Holiday... I'll take a look today So I'm an an idiot. Fixed it. #!/bin/bash is needed
December 27, 201411 yr Great, its starting now, but now I have what is probably a really silly question. I notice that it binds to port 4022, so does that mean i need to ssh into my server IP:4022? When i do so, it asks for a username and password which are different to the default port 22 root account of my server. When i SSH in to port 22 beets is not present. Can someone point me in the right direction as its possible i am doing it wrong...
December 28, 201411 yr Great, its starting now, but now I have what is probably a really silly question. I notice that it binds to port 4022, so does that mean i need to ssh into my server IP:4022? When i do so, it asks for a username and password which are different to the default port 22 root account of my server. When i SSH in to port 22 beets is not present. Can someone point me in the right direction as its possible i am doing it wrong... That one, I'm afraid, I don't know I've never used beets.
January 1, 201511 yr I also need help with this. I have got beets to install but the config directory is empty and only has a beets.sh file in it. Besides this I do not know how to proceed or open a web ui
January 1, 201511 yr it appears that beets does not offer a web interface it's all command line commands http://beets.readthedocs.org/en/v1.3.9/guides/index.html
January 1, 201511 yr I tried some of the commands, like for instance to import music folders etc. But it says beet: command not found.
January 1, 201511 yr I tried some of the commands, like for instance to import music folders etc. But it says beet: command not found. Are you using docker exec? docker exec NAMEOFCONTAINER COMMAND
January 2, 201511 yr When I try the command you just listed this is what I get: root@Tower:~# docker exec Beets beet Error: Command not found: exec Error: Command not found: Beets Usage: docker [OPTIONS] COMMAND [arg...] -H=[unix:///var/run/docker.sock]: tcp://host:port to bind/connect to or unix://path/to/socket to use A self-sufficient runtime for linux containers.
January 2, 201511 yr When I try the command you just listed this is what I get: root@Tower:~# docker exec Beets beet Error: Command not found: exec Error: Command not found: Beets Usage: docker [OPTIONS] COMMAND [arg...] -H=[unix:///var/run/docker.sock]: tcp://host:port to bind/connect to or unix://path/to/socket to use A self-sufficient runtime for linux containers. What version of unRAID are you on? Did you rename the container when installing it?
January 2, 201511 yr I am on 6 beta 10a. I didn't rename anything. Beets smdion/docker-beets:latest 12 minutes ago Up 5 minutes 192.168.1.83:4022->4022/tcp /mnt/user/Music/:/opt/downloads/music:rw /mnt/user/Music/Album Artists/:/opt/tmp:rw /mnt/cache/.apps/beets:/config:rw 750ae3123948 Updated smdion/docker-beets:latest Beets 24b54214f6bc 5 days ago 531.2 MB
January 2, 201511 yr I am on 6 beta 10a. I didn't rename anything. Beets smdion/docker-beets:latest 12 minutes ago Up 5 minutes 192.168.1.83:4022->4022/tcp /mnt/user/Music/:/opt/downloads/music:rw /mnt/user/Music/Album Artists/:/opt/tmp:rw /mnt/cache/.apps/beets:/config:rw 750ae3123948 Updated smdion/docker-beets:latest Beets 24b54214f6bc 5 days ago 531.2 MB Ahh thats why. Beta12 added "docker: update to 1.3.2". This is what brought in the "docker exec" command, which basically passes the command from unRAID to the container.
Archived
This topic is now archived and is closed to further replies.