Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Sebastien Arbogast
    @sarbogast
    laptop:sdc-docker sarbogast$ for i in `seq 1 3`; do export container_$i=`docker run --name couchbase-server-$i -d -P couchbase/server couchbase-start`; done
time="2015-05-01T10:11:49+02:00" level=fatal msg="Error response from daemon: problem creating container (09864558-e75e-45d2-9be8-0300c18e8d4c)" 
time="2015-05-01T10:11:50+02:00" level=fatal msg="Error response from daemon: problem creating container (3be0ae4d-bab8-45b0-ad3e-62d2f5e49032)" 
time="2015-05-01T10:11:51+02:00" level=fatal msg="Error response from daemon: problem creating container (d8db167d-7100-473b-8ece-e13efd63bb74)"
    Traun Leyden
    @tleyden

    Whats the easiest way to use hostname rather private ip address to join cluster?

    I don't think there's an easy way. I think one option would be to use the public ip here: https://github.com/tleyden/couchbase-cluster-go/blob/master/data/couchbase_node%40.service.template#L17 but I'm not even 100% sure that would work (would need testing)

    Another option you could consider is to create an ssh or open vpn tunnel from your data center to your boxes running in the AWS cloud.

    I have remove/add server back using hostname rather than private ip to walkaround this

    can you give details on what you mean exactly?

    @manyan if you need something exposed up as a parameter that will fix your issue, let me know. for example the ability to customize values in any of the service.template files.
    Traun Leyden
    @tleyden
    @sarbogast I think you want to ping the Joyent folks about that.
    @sarbogast there's no way to debug, because it didn't even return a container id

    if anyone wants to look over this and give feedback, would be much appreciated:

    https://github.com/couchbase/docker/blob/master/generate/resources/couchbase-server/README.md

    Traun Leyden
    @tleyden
    Don't forget to read the fine print on Joyent's container cloud — you will be charged for stopped containers!
    manyan.chen
    @manyan
    @tleyden to use hostname rather than ip, 1) remove node 2) rebalance 3) add the node back using hostname. for a 3 nodes cluster is "ok", but for a huge cluster, i don't think its suitable. I will try the public ip first, cheers
    Traun Leyden
    @tleyden
    Looks like there will be at least one speaker from Joyent at Couchbase Connect
    Traun Leyden
    @tleyden
    I've updated the blog post to use the couchbase/docker images.
    Traun Leyden
    @tleyden
    Anyone interested in Couchbase + Joyent, please check out http://tleyden.github.io/blog/2015/05/05/running-couchbase-server-under-docker-on-joyent/ and give me feedback
    Sebastien Arbogast
    @sarbogast
    @tleyden in the "Setup first couchbase node" command, what is the difference between both usernames/passwords in the command? do they have to be the same? which is for what?
    Traun Leyden
    @tleyden
    Ah I need to clarify that. First set is what you want them to be, so change those. Second set is initial/default, so use the ones given
    Sebastien Arbogast
    @sarbogast
    admin/password are the defaults? I just finished the procedure with custom values for both password (the same for Administrator as for admin) and it seems to have worked
    Traun Leyden
    @tleyden
    Yes, admin/password are the defaults
    Sebastien Arbogast
    @sarbogast
    then it should not have worked with a custom password for admin, should it?
    Sebastien Arbogast
    @sarbogast
    also, at the end of the procedure, if I run 'docker ps- -a' I see 8 containers, including 5 that have exited. I'm guessing those 5 are from all the commands that I ran to initialize the cluster, but won't they incur additional charges if I don't remove them?
    Traun Leyden
    @tleyden
    Great catch!
    Yup, you will be charged
    I need to update to add -rm flag
    Btw did you hear that joyent will present at Cb Connect?
    Sebastien Arbogast
    @sarbogast
    no I didn't know
    too bad I can't join
    Traun Leyden
    @tleyden
    Bryan Cantrill is slated to give a keynote, and a couple other Joyet folks will be coming to Connect. You can watch the videos after the conference.
    Sebastien Arbogast
    @sarbogast
    awesome
    I mean it's good if they make it easier to deploy couchbase to the cloud but hopefully this will make it worth the effort for Couchbase to tackle other kinds of customers ;)
    Traun Leyden
    @tleyden
    Joyent is on prem too. (A lot of enterprise customers require on prem)
    I'm also working on getting couchbase working on kubernetes: https://github.com/tleyden/couchbase-kubernetes
    Theoretically that could also run on Joyent, but I dont think they support Kubernetes out of the box yet. I've been testing on Google Container Engine (GKE)
    Sebastien Arbogast
    @sarbogast
    I know, but startups are rarely on prem, startups don't want to have to deal with all that infrastructure stuff, for us, infrastructure is a commodity, and spending thousands of dollars on our own data centers, and paying consultants 2500 bucks a day to help us set that all up is just overkill
    very good keynote in Devoxx France this year about this: http://fr.slideshare.net/quentinadam/the-end-of-server-management-hosting-have-to-become-a-commodity-keynote-devoxx-fr-2015
    Traun Leyden
    @tleyden
    You are talking to a prev startup cofounder who ran everything on heroku ;)
    Sebastien Arbogast
    @sarbogast
    Heroku for couchbase sync si sooooo the future!
    manyan.chen
    @manyan
    @tleyden can you provide a command to start/restart a couchbase node using docker? one of the node went down last night, as you can see the docker ps return me empty list, would like to restart it, but can no find the command, cheers
    Traun Leyden
    @tleyden
    @manyan sorry, just now seeing your message.
    @manyan can you give me a little more background on how you are running it? Is this under coreos? let me know the blog post or instructions you are working off of
    Traun Leyden
    @tleyden
    @PaulCapestany the coreos/fleet stuff is broken for me too: couchbaselabs/couchbase-server-coreos#17. I'm pretty sure I broke things when I made some changes to make things work with Kubernetes.
    Traun Leyden
    @tleyden
    ok, fixed and I the instructions have been consolidated into this README
    Paul Capestany
    @PaulCapestany
    @tleyden just now seeing your message, I seemed to still run into issues even with updated code + README → couchbaselabs/couchbase-server-coreos#18
    Traun Leyden
    @tleyden
    can you paste the output of "docker log afd91d66eab3"?
    (the container id of the sync gw container that seems to have failed)
    or fleetctl journal --lines 1000 sync_gw_node@1.service
    Paul Capestany
    @PaulCapestany
    sure
    oh, hmm, already killed off that cluster, starting up a new one
    Paul Capestany
    @PaulCapestany
    @tleyden — I just edited couchbaselabs/couchbase-server-coreos#18 and updated all the log files with info from a brand new cluster (and added extra stuff you'd asked for)
    Traun Leyden
    @tleyden
    ok thanks. something is breaking down in this code: https://github.com/tleyden/couchbase-cluster-go/blob/434233287e6af401a8a165dc92144d94e85c6e34/cmd/sync-gw-config/sync-gw-config.go#L48-L91
    I'm surprised that the config emitted had "server":"http://127.0.0.1:8091", rather than {{ .COUCHBASE_IP }}, though I don't know if that's the root problem
    Traun Leyden
    @tleyden
    that whole approach of rewriting the file from a template feels super hacky.
    I guess the thing writing the file is probably writing it one place, and thing reading the file is looking for it in a different place... what those places are is not immediately apparent.