14:48:12 GMT <Diplomat> hey guys, does anyone have any experience with redis official docker image ?
15:00:49 GMT <ahfeel> Diplomat: Mh, you can ask maybe I can help :)
15:01:48 GMT <Diplomat> ahfeel: Well, I think it's my server problem right now.. basically my docker image times out on master server replication
15:01:54 GMT <Diplomat> But works fine outside of the docker image
15:02:09 GMT <Diplomat> I mean redis-cli -h MASTER works perfectly.. so firewall doesn't block it
15:02:54 GMT <Diplomat> so I'm trying with a new VM .. I was testing with AWS ECS AMI and I finally noticed that it gave me iptables error.. so Im using AWS default ami maybe it helps
15:07:27 GMT <Diplomat> yeah, that was the case.. weird
15:14:44 GMT <ahfeel> Diplomat: mh ok :|
15:52:31 GMT <minus> yeah, that has less to do with redis more with sysadminning
16:10:35 GMT <Diplomat> So yea, I got it solved, but now I'm trying to connect to redis from another container, but it doesn't want to work. When I'm using --net=host then redis works perfectly, but when I'm linking them together it gives me connection reset by peer
16:10:54 GMT <Diplomat> I'm running redis like: docker run -itd -p 6379:6379 --name=redis redis
16:12:46 GMT <Diplomat> When I attach to my main container and do : telnet redis 6379 it tells me: telnet: Unable to connect to remote host: Connection refused
16:13:13 GMT <Diplomat> and when I'm doing redis-cli outside of the container it tells me: Error: Connection reset by peer
16:14:00 GMT <Schwarzbaer> Diplomat, unrelated, but still -itd? Interactive *and* detached?
16:14:44 GMT <Diplomat> I'm a bit noob at docker so I found it from some example.. so I used it, I can remove it
16:14:52 GMT <Schwarzbaer> Also the host "redis" is probably just not known in the container itself?
16:15:05 GMT <Diplomat> Via linking it can resolve it
16:15:22 GMT <Diplomat> root@3e012bed0375:/# telnet redis 6379
16:15:22 GMT <Diplomat> Trying 172.17.0.2...
16:15:22 GMT <Diplomat> telnet: Unable to connect to remote host: Connection refused
16:15:39 GMT <Schwarzbaer> Try telnet localhost 6379?
16:15:59 GMT <Diplomat> One moment
16:16:58 GMT <Diplomat> telnet: Unable to connect to remote host: Connection refused
16:17:03 GMT <Schwarzbaer> For that matter, apparently your container's hostname isn't redis, but 3e012bed0375
16:17:15 GMT <Schwarzbaer> Huh. that's... interesting.
16:17:25 GMT <Diplomat> Yes, because I'm connecting from my other container which needs to talk with redis
16:18:30 GMT <ahfeel> Diplomat: your containers have to share the same network or to be explicitely linked to each others
16:18:52 GMT <ahfeel> Diplomat: you should have a look at docker-composer to build your stack
16:19:14 GMT <ahfeel> Diplomat: otherwise, you have to explicitely publish the port to be open on the host
16:19:38 GMT <ahfeel> Diplomat: but the DNS resolution wont happen magically
16:20:12 GMT <ahfeel> Diplomat: Linking them with docker-compose or through the name network will make DNS resolution work
16:20:20 GMT <Diplomat> uno momento
16:20:22 GMT <Diplomat> ill try
16:22:52 GMT <Schwarzbaer> ahfeel, docker-compose is the middle ground between Kubernetes and starting each container by hand?
16:27:02 GMT <ahfeel> Schwarzbaer: yeah ! :)
16:27:18 GMT <ahfeel> It's a simple way to describe how a few containers should be launched and interact together
16:27:55 GMT <Schwarzbaer> Nice. I've pushed it on my "Look at that!" stack. Any other recommendations on what tools I should know when working with Docker?
16:29:16 GMT <ahfeel> Schwarzbaer: depends on how "big" your setup is, but if you manage a few servers I recommend checking out Rancher
16:29:19 GMT <ahfeel> :)
16:30:46 GMT <Schwarzbaer> Currently it's just a matter of "I want to build up and tear down environments for testing purposes", but it might soon evolve into "And now let's deploy it in the wild, too."
16:30:50 GMT <Diplomat> Hmn, so I added links: - redis:redis to my main app, but it doesn't want to resolve "redis"
16:33:53 GMT <Diplomat> Here's my compose file btw: http://paste.ofcode.org/4geaUEeHVJdaKiJeAYXN5Y
17:25:27 GMT <niks> Hello everyone, i'm working on a project and would like to know if i can do something with redis before starting to learn it(as i'm kind of short on time). The idea would be to use redis with RubyOnRails and ActionCable, so i have a realtime update on some variables though 5-10 webclients, and in the same time have a local app that update those same variables from time to time. For example : I have a "intensity" variable that is an inte
17:25:27 GMT <niks> ger that goes from 1 to 100, I can have 5 webclient that can change this value and see this value change in realtime(via RubyOnRails), but also have a local app that can change it and make it change in realtime on the web clients and all.  For now, I built a RoR website that use ActionCable and redis with a value that is updated in realtime and all, but when i run a "redis-cli" on my computer and use the "keys *" commad, I get null.
17:32:06 GMT <niks> If not possible, what technology would you recommand me if a value has to be change in real time between a local application and 5-10 webclients?
17:32:55 GMT <minus> redis offers pubsub, or alternatively notifications (via pubsub) when a key changes
17:33:28 GMT <minus> first of all i wouldn't write RoR and realtime in the same sentence *runs away*
17:36:04 GMT <niks> yeah, I'm thinking more and more about having a node server running just for this task and a rails server running for all the rest ...(as I have a kinda big rails project already)
17:38:41 GMT <niks> I know redis has a pubsub, and that's the main idea why i want to use Redis, but I don't know how I can connect to the same redis namespace/server/whatever than my rails app(as I said, i'm new to redis, i only read about it before yesterday). For now it looks like rails have a "private channel" on the redis server to transfer data(i hope i am wrong or i hope i can get into this private channel somehow from outside rails)
18:02:06 GMT <Schwarzbaer> ahfeel, docker-compose assumes that there's no manual setup needed per container? On one hand, that'd be sensible, on the other, there's Sentry's somewhat b0rked way of setting up things.
18:10:31 GMT <ahfeel> Schwarzbaer: Sentry ?
18:12:46 GMT <Schwarzbaer> ahfeel, an error logging server. So you know what *exactly* goes wrong in your application.
18:13:20 GMT <Schwarzbaer> But apparently I've just set it up wrong... I think. Maybe. I don't know. I guess I'll try again later.