Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Linux support #696

Merged
merged 5 commits into from
Dec 1, 2015
Merged

Linux support #696

merged 5 commits into from
Dec 1, 2015

Conversation

zedtux
Copy link
Contributor

@zedtux zedtux commented Jun 22, 2015

This branch add the missing Linux support.

Basically it avoid the wizard to run and force dockerode to use /var/run/docker.sock as a socketPath.

Regarding the in-container-shell only the GNOME terminal has been implemented (as I'm using Debian) but a warning message asking to open an issue in the project will be shown in other cases so that we can implement them one after the other.

The missing part of this merge request is the packaging. I don't really want to deal with that and let packagers taking care of this task but I'm available to help in case of questions and Grunt task fabrication.

@zedtux zedtux mentioned this pull request Jun 22, 2015
@entropitor
Copy link

💯 for @zedtux's amazing work.

@zedtux
Copy link
Contributor Author

zedtux commented Jun 22, 2015

Tank you @caske33 !!

@pgasiorowski
Copy link

Hell yeah!

@jmorganca
Copy link
Contributor

INCREDIBLE to see this during DockerCon! Awesome!

Taking a look on my ubuntu machine. Exciting!

@entropitor
Copy link

@zedtux Maybe you should also update the readme to say that it also supports linux :)

@zedtux
Copy link
Contributor Author

zedtux commented Jun 25, 2015

It's done @caske33. The only thing is as we still need to work on the packaging, I'm not touching the parts about the download and uninstall.

@entropitor
Copy link

@zedtux Maybe a new issue should be created so this PR can be merged already?

@zedtux
Copy link
Contributor Author

zedtux commented Jun 25, 2015

Fine for me @caske33.

@mchiang0610
Copy link
Contributor

Getting some errors on fresh install of ubuntu 14.04

npm http GET https://registry.npmjs.org/estraverse
npm http GET https://registry.npmjs.org/chromium-pickle/0.1.4
npm http GET https://registry.npmjs.org/walkdir/0.0.7
npm http 304 https://registry.npmjs.org/number-is-nan
npm http 304 https://registry.npmjs.org/optionator
npm http 304 https://registry.npmjs.org/estraverse
npm http 304 https://registry.npmjs.org/esutils
npm http 304 https://registry.npmjs.org/walkdir/0.0.7
npm http 304 https://registry.npmjs.org/chromium-pickle/0.1.4

> electron-prebuilt@0.27.3 postinstall /home/mc/workspace/kitematic/node_modules/electron-prebuilt
> node install.js

npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm http GET https://registry.npmjs.org/fast-levenshtein
npm http GET https://registry.npmjs.org/levn
npm http GET https://registry.npmjs.org/prelude-ls
npm http GET https://registry.npmjs.org/deep-is
npm http GET https://registry.npmjs.org/type-check
npm http GET https://registry.npmjs.org/bindings/1.1.0
npm http GET https://registry.npmjs.org/native-mate/0.2.6
npm ERR! weird error 1
npm http 304 https://registry.npmjs.org/levn
npm http 304 https://registry.npmjs.org/prelude-ls
npm http 304 https://registry.npmjs.org/deep-is
npm ERR! tar pack Error reading /home/mc/tmp/npm-16732-cRIen8rF/1434904985038-0.3272380668204278/package
npm ERR! addLocalDirectory Could not pack "/home/mc/tmp/npm-16732-cRIen8rF/1434904985038-0.3272380668204278/package" to "/home/mc/.npm/babel-core/5.6.11/package.tgz"
npm http 304 https://registry.npmjs.org/native-mate/0.2.6

> contextify@0.1.14 install /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/jsdom/node_modules/contextify
> node-gyp rebuild

npm http 304 https://registry.npmjs.org/bindings/1.1.0
npm http 304 https://registry.npmjs.org/type-check
npm http GET https://registry.npmjs.org/native-mate/-/native-mate-0.2.6.tgz
npm http 304 https://registry.npmjs.org/fast-levenshtein
npm http GET https://registry.npmjs.org/domelementtype
npm http GET https://registry.npmjs.org/domhandler
npm http GET https://registry.npmjs.org/domutils
npm http GET https://registry.npmjs.org/entities
npm http 200 https://registry.npmjs.org/native-mate/-/native-mate-0.2.6.tgz
npm http GET https://registry.npmjs.org/argparse
gyp: Call to 'node -e "require('nan')"' returned exit status 1. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.16.0-41-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/jsdom/node_modules/contextify
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! Error: ENOENT, lstat '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/jsdom/node_modules/cssstyle/lib/properties.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.16.0-41-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/mc/workspace/kitematic
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/jsdom/node_modules/cssstyle/lib/properties.js
npm ERR! fstream_path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/jsdom/node_modules/cssstyle/lib/properties.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/async'
npm ERR! error rolling back  jest-cli@0.4.13 { [Error: ENOTEMPTY, rmdir '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/async']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/async' }
npm ERR! Error: ENOENT, lstat '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/handlebars/dist/handlebars.runtime.amd.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.16.0-41-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/mc/workspace/kitematic
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/handlebars/dist/handlebars.runtime.amd.js
npm ERR! fstream_path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/handlebars/dist/handlebars.runtime.amd.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/escodegen/node_modules/source-map/test/source-map/test-source-map-generator.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.16.0-41-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/mc/workspace/kitematic
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/escodegen/node_modules/source-map/test/source-map/test-source-map-generator.js
npm ERR! fstream_path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/escodegen/node_modules/source-map/test/source-map/test-source-map-generator.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm http 304 https://registry.npmjs.org/domelementtype
npm http 304 https://registry.npmjs.org/argparse
npm http 304 https://registry.npmjs.org/domhandler
npm http 304 https://registry.npmjs.org/domutils
npm http 304 https://registry.npmjs.org/entities
npm ERR! error rolling back Error: ENOTEMPTY, rmdir '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/js-yaml/node_modules/argparse'
npm ERR! error rolling back  istanbul@0.3.16 { [Error: ENOTEMPTY, rmdir '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/js-yaml/node_modules/argparse']
npm ERR! error rolling back   errno: 53,
npm ERR! error rolling back   code: 'ENOTEMPTY',
npm ERR! error rolling back   path: '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/js-yaml/node_modules/argparse' }
npm http GET https://registry.npmjs.org/dom-serializer
npm http 304 https://registry.npmjs.org/dom-serializer
npm ERR! Error: ENOENT, lstat '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/js-yaml/node_modules/esprima/esprima.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.16.0-41-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/mc/workspace/kitematic
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/js-yaml/node_modules/esprima/esprima.js
npm ERR! fstream_path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/js-yaml/node_modules/esprima/esprima.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/node-haste/node_modules/esprima-fb/test/test.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.16.0-41-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/mc/workspace/kitematic
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/node-haste/node_modules/esprima-fb/test/test.js
npm ERR! fstream_path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/node-haste/node_modules/esprima-fb/test/test.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/escodegen/node_modules/esprima/test/test.js'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.16.0-41-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /home/mc/workspace/kitematic
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/escodegen/node_modules/esprima/test/test.js
npm ERR! fstream_path /home/mc/workspace/kitematic/node_modules/jest-cli/node_modules/istanbul/node_modules/escodegen/node_modules/esprima/test/test.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)

> native-mate@0.2.6 install /home/mc/workspace/kitematic/node_modules/grunt-electron-installer/node_modules/asar/node_modules/chromium-pickle/node_modules/native-mate
> echo



> chromium-pickle@0.1.4 install /home/mc/workspace/kitematic/node_modules/grunt-electron-installer/node_modules/asar/node_modules/chromium-pickle
> node-gyp rebuild

gyp: Call to 'node -e "require('native-mate')"' returned exit status 1. while trying to load binding.gyp
gyp ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:797:12)
gyp ERR! System Linux 3.16.0-41-generic
gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/mc/workspace/kitematic/node_modules/grunt-electron-installer/node_modules/asar/node_modules/chromium-pickle
gyp ERR! node -v v0.10.25
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok 
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/mc/workspace/kitematic/npm-debug.log
npm ERR! not ok code 0

@zedtux
Copy link
Contributor Author

zedtux commented Jun 26, 2015

Can you post all the commands you've run ?

On my Debian box, I'm running:

$ make
$ sudo npm start

And it's working.

@zedtux
Copy link
Contributor Author

zedtux commented Jun 29, 2015

What is missing in order to merge this pull request ?

@TeckniX
Copy link
Contributor

TeckniX commented Jun 29, 2015

@zedtux With DockerCon last week there hasn't been much time to QA your PR - I'll take a look at it today.
Thanks for your patience!

@TeckniX
Copy link
Contributor

TeckniX commented Jun 29, 2015

Can you provide your version of NPM and NODEJS - Seem I'm already getting some dependency issues.
We may need to provide a guide/readme for users to upgrade their version of node+npm to the latest.

@TeckniX
Copy link
Contributor

TeckniX commented Jun 29, 2015

Just to give you an idea of my steps so far from a vanilla install of 14.04 LTS

$ sudo apt-add-repository ppa:chris-lea/node.js
$ sudo apt-get update
$ sudo apt-get install build-essential
$ sudo apt-get install nodejs

This may be basic stuff, but it will probably need to be added in the docs for it to boot up.

Also it seems that your current setup doesn't install docker? or it fails to install because of suid?
Here are some screenshots from this recent install:

npm-logs

ubuntu-docker

@entropitor
Copy link

@TeckniX chrislea is an old ppa. You should probably download node from nodesource: https://nodesource.com/blog/chris-lea-joins-forces-with-nodesource

curl -sL https://deb.nodesource.com/setup | sudo bash -

@zedtux
Copy link
Contributor Author

zedtux commented Jul 1, 2015

Sorry @TeckniX but it's a bite tricky for me to work on Linux and provide features for the OS X / Windows version.

I've just moved and my iMac is still in his box (yes .. what a shame !! :D) but I will tell you my versions as soon as possible. Now you should probably discuss more with @caske33 who's using Ubuntu (I'm using Debian).

Finally, regarding the second screenshot you've posted, it looks like you didn't used sudo in order to start Kinematic.

@TeckniX
Copy link
Contributor

TeckniX commented Jul 1, 2015

@zedtux no need to add features for osx/windows, I just want to get ubuntu in there and working!

The error is more likely to be related to the missing docker daemon - When Kitematic starts (on OSX/windows) it creates a VM to allow docker to function properly, as seen in the Setup.js:
https://github.com/zedtux/kitematic/blob/linux-support/src/stores/SetupStore.js#L153

IMHO the Linux distro should do the same, although it can simply install/setup the docker daemon locally. Usually installed in /usr/local/bin since it won't be a managed package. (unless I missed where this is setup in your PR?)

@zedtux
Copy link
Contributor Author

zedtux commented Jul 3, 2015

no need to add features for osx/windows, I just want to get ubuntu in there and working!

Sorry I wasn't clear. I'm talking about me, developing things like the editable volumes... I'm developing on Linux, but I can't include the Linux support in the editable volumes branch, so I have to do some tricking things in order to developer under Linux and provide the feature for the official repository.

The error is more likely to be related to the missing docker daemon - When Kitematic starts (on OSX/windows) it creates a VM to allow docker to function properly, as seen in the Setup.js:
https://github.com/zedtux/kitematic/blob/linux-support/src/stores/SetupStore.js#L153

IMHO the Linux distro should do the same, although it can simply install/setup the docker daemon locally. Usually installed in /usr/local/bin since it won't be a managed package. (unless I missed where this is setup in your PR?)

The PR is not installing Docker as it has to be done using the package manager. This is quite a big job to implement as it should manage all the different Linux distribution.

The purpose of this PR is not to make Kitematic working on a fresh Linux box, it's about to make Kitematic working on Linux, meaning you have a step before which is to make sure Docker is running on your machine.

But I fully agree with you that at the end of the day, Kitematic on Linux should take care to install Docker automagically.

@zedtux
Copy link
Contributor Author

zedtux commented Jul 5, 2015

And BTW the Docker installation should be done as a dependency of the Kitematic package. There's no need for a wizard.

@zedtux zedtux mentioned this pull request Jul 6, 2015
@TeckniX
Copy link
Contributor

TeckniX commented Jul 6, 2015

@zedtux in regards to this:

But I fully agree with you that at the end of the day, Kitematic on Linux should take care to install Docker automagically.

I agree 100% and it's what Kitematic does on Windows/Mac - As mentioned your PR disabled this as seen at the following line:
https://github.com/zedtux/kitematic/blob/linux-support/src/stores/SetupStore.js#L153

@entropitor
Copy link

@TeckniX what @zedtux is trying to say is that it shouldn't be done through the code but through the .deb, .rpm packages etc, which should have a dependency of the docker executable.

The packages is something that still needs work, but we'll need help from someone with experience with .deb and .rpm packages.

If you do this through code, you want have to check which package manager is installed, and then use the correct one. That's cubersome and shouldn't be done in code anyway. It should be in the .deb/.rpm package.

@TeckniX
Copy link
Contributor

TeckniX commented Jul 6, 2015

@caske33 I didn't envision the rpm install kitematic and see what you're saying.

Although the same argument could be made with brew install kitematic (not how it's currently installed), Kitematic should still check for the appropriate docker tools and install them if missing or need to be updated for the OS it's currently running on.

ps: Obviously this is my opinion only based on how Kitematic currently works and the need to keep things homogeneous. (aka it does/checks the same thing on all platforms)

@entropitor
Copy link

The problem with linux is that you have a lot more ways of installing docker. Take a look at http://docs.docker.com/installation/. Only 1 of them is windows and 1 is Mac OS X. But you've got a couple of install guides for linux based distro's. That's why, for the maintainability of the feature, I suggest NOT to implement it in the code itself.

However, maybe some sort of dialog box could be displayed if docker isn't installed? (maybe with link to the page I referenced earlier) so people can install it manually?

@TeckniX
Copy link
Contributor

TeckniX commented Jul 6, 2015

I would be ok with that approach, although I believe most users using Kitematic would be on an ubuntu-like system - Basically let the user know that docker needs to be installed and provide a link to that page, if we don't detect an 'ubuntu' distro?

Maybe this could show up where the VM error usually shows up? @zedtux what do you think?

Edit:
This would work for 99% of the users:
wget -qO- https://get.docker.com/ | sh

@pgasiorowski
Copy link

After merging the PR it works nicely on ubuntu 14.10.
Thanks for all the work!

@mickaelandrieu
Copy link

nice ! thank you for your contribution @zedtux

@TeckniX
Copy link
Contributor

TeckniX commented Jul 6, 2015

Some additional feedback after installing docker from the above 'wget' command:

  • Remove "Install Docker Commands" from the 'Kitematic' menu (should already be installed)
  • Clicking on Kitematic > About creates the following error for me:

"Uncaught Exception:
TypeError: Menu.sendActionToFirstResponder is not a function
at MenuItem.click (/home/user/kitematic/node_modules/electron-prebuilt/dist/resources/atom.asar/browser/api/lib/menu-item.js:46:25)
at Function.delegate.executeCommand (/home/user/kitematic/node_modules/electron-prebuilt/dist/resources/atom.asar/browser/api/lib/menu.js:127:69)"

gist: https://gist.github.com/anonymous/d218e9f78725d53c91eb

@jmorganca
Copy link
Contributor

Almost there!

@zedtux
Copy link
Contributor Author

zedtux commented Nov 24, 2015

Thanks @JeffDM but it's no more working ... 😮

@zedtux
Copy link
Contributor Author

zedtux commented Nov 24, 2015

Ho ... no ..it's fine :) sorry, I'm pushing ...

@jmorganca
Copy link
Contributor

That one last comment and then that's it from me. Amazing work @zedtux!

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

@JeffDM the change is done. All seems to work still.

@ryanleesipes
Copy link

Followed the install here https://github.com/docker/kitematic/wiki/Early-Linux-Support - got the following error. What am I doing wrong? Let me know if I just screwed up somewhere.
screenshot from 2015-12-01 08-27-32

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

Thanks @ryanleesipes for having reported this. I'll have a look at it.

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

@ryanleesipes it's wired. I don't have this error.

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

@ryanleesipes I think you found a bug in Kitematic. I don't have the error raised, but I can see the bug. The file components/ContainerLogs.react is imported in the routes.js file but this file doesn't exists nor in my branch, nor in the Kitematic master branch.

@jmorganca
Copy link
Contributor

LGTM

jmorganca pushed a commit that referenced this pull request Dec 1, 2015
@jmorganca jmorganca merged commit dc8b360 into docker:master Dec 1, 2015
@FrenchBen
Copy link
Contributor

Woohoo!!! Congrats @zedtux for pushing on this. All merged now 🎉

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

Whhoooo !! I'm so proud of this ! Amwesome ! Thank you so much @JeffDM, @FrenchBen, @mchiang0610 and @TeckniX ! 💪 🤘

@master-lincoln
Copy link

Thank you @zedtux for being so persistent on this...well appreciated

@thaJeztah
Copy link
Member

Oh, cool! Thanks @zedtux!!

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

You're welcome @master-lincoln and @thaJeztah 🙇

@jmorganca
Copy link
Contributor

@zedtux awesome to see this merged! Thank you so much!

@zedtux
Copy link
Contributor Author

zedtux commented Dec 1, 2015

And thank you for having guide me in the last moments :)

@entropitor
Copy link

@zedtux I'm happy to see this merged 🎉 ! I think you helped a lot of people. Thank you for keeping up the good work! 💯

@zedtux
Copy link
Contributor Author

zedtux commented Dec 2, 2015

Thank you @caske33, I'm glade to help people.

@zedtux
Copy link
Contributor Author

zedtux commented Dec 2, 2015

@ryanleesipes the bug you found has been fixed in this commit by @JeffDM

@ryanleesipes
Copy link

@zedtux fantastic. Thanks for pointing me at that! :)

@ryanleesipes
Copy link

Everything is working great. Anyone aware of any efforts to put this in a PPA?

@zedtux
Copy link
Contributor Author

zedtux commented Dec 2, 2015

@ryanleesipes @FrenchBen is working on it I believe.

@timfallmk
Copy link

Woohoo! Horray for getting this one!
On Wed, Dec 2, 2015 at 10:26 Guillaume Hain notifications@github.com
wrote:

@ryanleesipes https://github.com/ryanleesipes @FrenchBen
https://github.com/FrenchBen is working on it I believe.


Reply to this email directly or view it on GitHub
#696 (comment).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.