Hi All,

 

I have been looking at implementing this https://hub.docker.com/r/subzero79/docker-telegram-couchpotato-bot/ into an unRAID Docker.  I am wondering if it is an easy to implement since it is already dockerized or not.  I try to manually add it through the WebUI and get an error about not specifying arguments, and I am able to add the Docker by running:

 

docker run -d --name=telegram-bot --restart=always subzero79/docker-telegram-couchpotato-bot -v /mnt/cache/appdata/taterbot:/config

 

It pulls the docker data but then comes back with this error:

 

Error response from daemon: Cannot start container e4ceab4b6b3fbaa2b0a6973ef61f549f40fb30213e6fc93cf27fcb6acd67592d: [8] System error: exec: "-v": executable file not found in $PATH

 

I am sure I am missing something simple, and I'm happy to research this more on my own, but would love any advice on how to add this docker to unRAID.

 

TIA!

Hi All,

 

I have been looking at implementing this https://hub.docker.com/r/subzero79/docker-telegram-couchpotato-bot/ into an unRAID Docker.  I am wondering if it is an easy to implement since it is already dockerized or not.  I try to manually add it through the WebUI and get an error about not specifying arguments, and I am able to add the Docker by running:

 

docker run -d --name=telegram-bot --restart=always subzero79/docker-telegram-couchpotato-bot -v /mnt/cache/appdata/taterbot:/config

 

It pulls the docker data but then comes back with this error:

 

Error response from daemon: Cannot start container e4ceab4b6b3fbaa2b0a6973ef61f549f40fb30213e6fc93cf27fcb6acd67592d: [8] System error: exec: "-v": executable file not found in $PATH

 

I am sure I am missing something simple, and I'm happy to research this more on my own, but would love any advice on how to add this docker to unRAID.

 

TIA!

Not quite sure, but if you enable dockerHub searches within Community Applications, then search for that container, it will add and run it.

Hi All,

 

I have been looking at implementing this https://hub.docker.com/r/subzero79/docker-telegram-couchpotato-bot/ into an unRAID Docker.  I am wondering if it is an easy to implement since it is already dockerized or not.  I try to manually add it through the WebUI and get an error about not specifying arguments, and I am able to add the Docker by running:

 

docker run -d --name=telegram-bot --restart=always subzero79/docker-telegram-couchpotato-bot -v /mnt/cache/appdata/taterbot:/config

 

It pulls the docker data but then comes back with this error:

 

Error response from daemon: Cannot start container e4ceab4b6b3fbaa2b0a6973ef61f549f40fb30213e6fc93cf27fcb6acd67592d: [8] System error: exec: "-v": executable file not found in $PATH

 

I am sure I am missing something simple, and I'm happy to research this more on my own, but would love any advice on how to add this docker to unRAID.

 

TIA!

Not quite sure, but if you enable dockerHub searches within Community Applications, then search for that container, it will add and run it.

 

That did it, thanks!

Hi All,

 

I have been looking at implementing this https://hub.docker.com/r/subzero79/docker-telegram-couchpotato-bot/ into an unRAID Docker.  I am wondering if it is an easy to implement since it is already dockerized or not.  I try to manually add it through the WebUI and get an error about not specifying arguments, and I am able to add the Docker by running:

 

docker run -d --name=telegram-bot --restart=always subzero79/docker-telegram-couchpotato-bot -v /mnt/cache/appdata/taterbot:/config

 

It pulls the docker data but then comes back with this error:

 

Error response from daemon: Cannot start container e4ceab4b6b3fbaa2b0a6973ef61f549f40fb30213e6fc93cf27fcb6acd67592d: [8] System error: exec: "-v": executable file not found in $PATH

 

I am sure I am missing something simple, and I'm happy to research this more on my own, but would love any advice on how to add this docker to unRAID.

 

TIA!

 

for everybody's reference:

docker <cmd> [options] <docker-image> [command]

 

do it should have been

docker run -d --name=telegram-bot --restart=always -v /mnt/cache/appdata/taterbot:/config subzero79/docker-telegram-couchpotato-bot

Hi All,

 

I have been looking at implementing this https://hub.docker.com/r/subzero79/docker-telegram-couchpotato-bot/ into an unRAID Docker.  I am wondering if it is an easy to implement since it is already dockerized or not.  I try to manually add it through the WebUI and get an error about not specifying arguments, and I am able to add the Docker by running:

 

docker run -d --name=telegram-bot --restart=always subzero79/docker-telegram-couchpotato-bot -v /mnt/cache/appdata/taterbot:/config

 

It pulls the docker data but then comes back with this error:

 

Error response from daemon: Cannot start container e4ceab4b6b3fbaa2b0a6973ef61f549f40fb30213e6fc93cf27fcb6acd67592d: [8] System error: exec: "-v": executable file not found in $PATH

 

I am sure I am missing something simple, and I'm happy to research this more on my own, but would love any advice on how to add this docker to unRAID.

 

TIA!

Not quite sure, but if you enable dockerHub searches within Community Applications, then search for that container, it will add and run it.

 

That did it, thanks!

 

Hey, I am also trying to add this docker.  Can you tell me what you searched for in Community Applications?  I changed the setting to search dockerhub but nothing returns when I search "Telegram," or "subzero79"

 

I tried manually adding this docker as well but it wouldnt launch.

Have you enabled the option to search dockerhub in the CA settings?

Have you enabled the option to search dockerhub in the CA settings?

And hit the button to get further results?

 

Thanks! I missed the big button "Get more results from dockerhub" 

 

Now, I know this an unsupported/untested docker with unraid but having an issue getting it to work.  Hoping someone has had some luck with getting this setup and can point me in the right direction.

 

I put a config.json file in the config path.  When I look at the logs, I see this:

 

2016-02-26 18:42:32,099 CRIT Supervisor running as root (no user in config file)

2016-02-26 18:42:32,103 INFO supervisord started with pid 8

2016-02-26 18:42:33,106 INFO spawned: 'telegram-couchpotato-bot' with pid 11

2016-02-26T18:42:33.529Z - [32minfo[39m: config file found /app/telegram-couchpotato-bot-master/lib/../config.json

2016-02-26 18:42:33,539 INFO exited: telegram-couchpotato-bot (exit status 1; not expected)

 

Thanks in advance.

 

EDIT: I made some more progress by finding an older config file to reference: {

  "telegram": {

    "botToken": ""

  },

  "bot": {

    "password": "SomePass",

    "owner": 0,

    "maxResults": 15

  },

  "couchpotato": {

    "hostname": "",

    "apiKey": "",

    "port": 5050,

    "urlBase": "",

    "ssl": false,

    "username": "",

    "password": ""

  }

}

 

My bot returned "Not authorized" to me.  So I set a password in the config file and attempted to /auth "password"

 

Now the log says:

 

016-02-26 19:45:04,475 INFO spawned: 'telegram-couchpotato-bot' with pid 74

2016-02-26T19:45:04.908Z - [32minfo[39m: config file found /app/telegram-couchpotato-bot-master/lib/../config.json

2016-02-26T19:45:04.913Z - [32minfo[39m: acl file found /app/telegram-couchpotato-bot-master/lib/../acl.json

2016-02-26T19:45:05.421Z - [33mwarn[39m: user: xxxxxxx message: You are not authorized to use this bot.

`/auth [password]` to authorize.

2016-02-26 19:45:05,436 INFO exited: telegram-couchpotato-bot (exit status 1; not expected)

2016-02-26 19:45:06,437 INFO gave up: telegram-couchpotato-bot entered FATAL state, too many start retries too quickly

I was able to get this docker to work correctly.  I was having troubles similar to you, but the config template that you posted seemed to do the trick. 

 

After I got it working, I went back trying to recreate the error you are seeing.  I am able to get the authorization error, but the bot continues to run (log shows line below).

 

2016-03-06 02:31:46,841 INFO success: telegram-couchpotato-bot entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

The only times that I now get the "exit status 1" error is when the syntax of the config file is not correct.  Maybe double check your config.json compared to the template you posted.