#docker-machine

/

      • cap10morgan has quit
      • wenlock joined the channel
      • cjellick has quit
      • cap10morgan joined the channel
      • vincent99 has quit
      • xi4ohui joined the channel
      • cap10morgan has quit
      • MHBauer has quit
      • bruienne has quit
      • bruienne_ joined the channel
      • slawrence00 has quit
      • torske has quit
      • torske joined the channel
      • xi4ohui has quit
      • wenlock joined the channel
      • andrewwatson joined the channel
      • andrewwatson has quit
      • andrewwatson joined the channel
      • leedm777 joined the channel
      • andrewwa_ joined the channel
      • andrewwatson has quit
      • ehazlett
        mapu do you have a firewall in place?
      • xi4ohuiliu joined the channel
      • generic joined the channel
      • shanse has quit
      • generic is now known as shanse
      • achanda joined the channel
      • leedm777 joined the channel
      • zhangyaqi joined the channel
      • leedm777 has quit
      • bruienne joined the channel
      • bruienne_ has quit
      • zhangyaqi has quit
      • helen_ joined the channel
      • andrewwa_ has quit
      • helen_ is now known as helen
      • helen is now known as Guest26281
      • Guest26281 has quit
      • helen_ joined the channel
      • helen_ has quit
      • cjellick joined the channel
      • helen_ joined the channel
      • helen_
        hello?
      • anyone here
      • xi4ohuiliu has quit
      • I have encountered a problem that terminal tell me that Error creating machine: exit status 1
      • You will want to check the provider to make sure the machine and associated resources were properly removed when I run ocker-machine create --driver virtualbox sec.
      • My os is fedora22.
      • would you help me? thx~
      • mbwe has quit
      • mbwe joined the channel
      • achanda joined the channel
      • leedm777 joined the channel
      • bruienne has quit
      • bruienne joined the channel
      • mbruzek has quit
      • leedm777 has quit
      • booyaa
        helen_: can you post the whole docker-machine create here
      • helen_ has quit
      • helen_ joined the channel
      • helen_
        booyaa: docker-machine create --driver virtualbox dev
      • I have just restarted systemd-modules-load.service and installed VirtualBox-devel.x86_64 in my dell. And now is ok.
      • spiderpug joined the channel
      • booyaa
        helen_: in future if docker fails even aftrer create
      • helen_
        so I am not sure which one cause that error.
      • booyaa
        try sticking it in debug mode i.e. docker-machine -D create/ssh/other docker command
      • helen_ is now known as zhangyaqi
      • virtualbox is a pre-req
      • so i suspect that's what fixed it
      • although it should've complained with a helpful error. i'll test on a system that doesn't have vbox installed
      • zhangyaqi
        Before i install VirtualBox-devel.x86_64 , i have installed VirtualBox.x86_64.
      • booyaa:^
      • booyaa
        ah so maybe the systemd restart triggered some kind of services that fedora needs to run virtualbox?
      • zhangyaqi
        booyaa: When I have seen that error,I run virtualbox in my terminal. And then the virtualbox client report that I should install VirtualBox-devel.x86_64 too.
      • booyaa
        yeah you get a very helpful error if it's not installed. mmm i guess the devel package provides the api hooks into vb
      • zhangyaqi
        booyaa: yeah, and now I want to reappear that error for finding the true reason. :) Thank you very much.
      • booyaa
        zhangyaqi: you're welcome :) enjoy machining!
      • zhangyaqi: you could do it in docker container, there's a fedora 22 image
      • zhangyaqi
        booyaa: good idea. And should I make a Dockerfile first?
      • booyaa
        don't even need to delve that deep, this should suffice: docker run -it fedora:22 bash
      • how are you installing machine?
      • zhangyaqi
        via curl
      • curl -L https://github.com/docker/machine/releases/down... > /usr/local/bin/docker-machine
      • booyaa
        ah straight from github then? good stuff
      • wow fedora has changed since i last used it, so yum is no longer the package manager?
      • zhangyaqi
        booyaa: yeah. dnf instead of yum.
      • booyaa: in fedora22
      • booyaa
        can't see those packages, wondering if there's different names for server and desktop?
      • achanda joined the channel
      • zhangyaqi
        booyaa: I don't quite understand what you mean. what packages? 0.0
      • achanda joined the channel
      • booyaa
        the search results for: dnf search virtualbox
      • bruienne has quit
      • bruienne joined the channel
      • there's two libvirt drivers and this RemoteBox.noarch : Open Source VirtualBox Client with Remote Management
      • zhangyaqi
        booyaa: should i install RemoteBox.noarch 。
      • AntonioMeireles has quit
      • booyaa
        mmm i'm wondering if you have to add the desktop package sites to get VirtualBox-devel.x86_64?
      • do you know where the equivalent of /etc/apt/sources.list is for ndf?
      • that's debian's config file for package repositories/sites
      • zhangyaqi
        booyaa: I think in the /etc/yum.repos.d
      • booyaa
        can you compare to your desktop? i'll see if i can find out about how to install virtualbox on a server version of fedora
      • might be a bit delayed because i have to go do my day job ;)
      • zhangyaqi
        booyaa: I think the reason is that virtualbox linux kernel driver isn't loaded.
      • see this :
      • [helen@localhost yum.repos.d]$ rpm -qa |grep -i virtualbox
      • kmod-VirtualBox-4.1.6-200.fc22.x86_64-4.3.30-1.fc22.x86_64
      • VirtualBox-kmodsrc-4.3.30-1.fc22.x86_64
      • python-VirtualBox-4.3.30-1.fc22.x86_64
      • VirtualBox-4.3.30-1.fc22.x86_64
      • VirtualBox-devel-4.3.30-1.fc22.x86_64
      • akmod-VirtualBox-4.3.30-1.fc22.x86_64
      • booyaa
        zhangyaqi: ah okay, that might be problematic then. you'd probably have to create your own image using fedora image build. might be quick just to create a virtualbox fedora image.
      • zhangyaqi
        booyaa: ok , I will try it. Thank you for your help. :)
      • AntonioMeireles joined the channel
      • booyaa
        zhangyaqi: yw
      • m451 joined the channel
      • bruienne_ joined the channel
      • bruienne has quit
      • cjellick joined the channel
      • cjellick has quit
      • m451 is now known as m451^AFK
      • OT: mmm wondering if the runc team are considering xhyve for osx interoperability? bruienne_ would this feasible? or am i getting the wrong end of the stick (again)?
      • Tebro_ is now known as Tebro
      • cjellick joined the channel
      • cjellick has quit
      • djx joined the channel
      • wenlock joined the channel
      • bruienne_ has quit
      • bruienne joined the channel
      • christyp joined the channel
      • mbruzek joined the channel
      • bruienne has quit
      • bruienne joined the channel
      • leedm777 joined the channel
      • cjellick joined the channel
      • cjellick has quit
      • miqui joined the channel
      • chuchunaku joined the channel
      • mbruzek has quit
      • mapu joined the channel
      • mbruzek joined the channel
      • chuchunaku has quit
      • cjellick joined the channel
      • cjellick has quit
      • cjellick joined the channel
      • miqui|2 joined the channel
      • alaindomissy joined the channel