Hey,

I have downloaded the windows binaries and try to start but:

$ ./kmachine.exe create -d virtualbox dev
Error loading driver "virtualbox": dial tcp 127.0.0.1:55016: connectex: Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée.

where

Aucune connexion n'a pu être établie car l'ordinateur cible l'a expressément refusée.

is

No connexion could be established because the targeted computer refused it

My use case for elastic ips is dns. So I can point Route53 to it,then kill/create the actual EC2 as many times as I want which is very useful for handling machine crashes

I think this is AWS specific. AFIK DO does not change the droplet ip when assigning a Floating ip but AWS does.

I have assigned a elastic ip to the EC2, and this changes the machine ip making the certs invalid.
52.67.88.239 is my elastic ip. Is there a way I can regenerate certs to a specific ip address like 52.67.88.239?

cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro
$ kmachine create -d amazonec2 --k8s-version 1.3.0-alpha.2 cescoferraro.xyz
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Rebooting system...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring kubernetes...
Copying certs tregenerate-certso the remote system...
To see how to connect Docker to this machine, run: kmachine env cescoferraro.xyz
cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro
$  kmachine env cescoferraro.xyz
Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "52.67.88.239:2376": x509: certificate is valid for 52.67.165.230, not 52.67.88.239

Currently regenerate-certs tries to ssh to the old ip

cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro
$ kmachine regenerate-certs cescoferraro.xyz
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Error getting SSH command: Something went wrong running an SSH command!
command : cat /etc/os-release
err     : exit status 255
output  :

Inter-container DNS resolution is not working. Are there plans to support this by enabling the DNS add-on ?

I'm interested in trying kmachine, but builds are failing, first because golang 1.5.1 is old and with latest it was still throwing an error during builds.

drivers/aurora/aurora.go:16:2: cannot find package "github.com/runseb/egoscale/src/egoscale" in any of:
/go/src/github.com/docker/machine/vendor/github.com/runseb/egoscale/src/egoscale (vendor tree)
/usr/local/go/src/github.com/runseb/egoscale/src/egoscale (from $GOROOT)
/go/src/github.com/runseb/egoscale/src/egoscale (from $GOPATH)
mk/build.mk:22: recipe for target 'build-x-machine-driver-aurora' failed
make: *** [build-x-machine-driver-aurora] Error 1
make: *** [cross] Error 2

Looks like aurora driver is gone from docker-machine, so I removed the driver and ran the build ok

so not to corrupt docker-machine
it's especially a pain for testing...

Hello, I keep getting the following error when I initiate "docker ps"

$ docker ps
Error response from daemon: client is newer than server (client API version: 1.2
4, server API version: 1.22)

$ docker version
Client:
Version: 1.12.0
API version: 1.24
Go version: go1.6.3
Git commit: 8eab29e
Built: Thu Jul 28 23:54:00 2016
OS/Arch: windows/amd64
Error response from daemon: client is newer than server (client API version: 1.2
4, server API version: 1.22)

I have tried kmachine upgrade dev but still the error is still coming.

Also when I initiate kubectl I get an error concerning certificate error:

$ kubectl get nodes
Error in configuration: unable to read certificate-authority C:\Program Files\Do
cker Toolbox\Userseadigbe.kubemachinemachinesdevca.pem for dev due to open C:\Pr
ogram Files\Docker Toolbox\Userseadigbe.kubemachinemachinesdevca.pem: The system
cannot find the file specified.

technically we should release in concert with k8s.
and update the kmachine -v output....when we release

Hi, as I rolled kmachine out on AWS I expected an expose to load balancer to create an ELB.

Not sure what it does when exposing to load balancer now.

Do I need to install/change something to get it to create an ELB?

When testing a default Kubernetes installation on AWS is does create an ELB on each expose to a load balancer.

Just spun a DO machine an realized it uses quite an old version of kubernetes. It there a way I could bump that?

cesco@laptop: ~/code/go/src/github.com/cescoferraro/spotify on master [!]
$ k version
Client Version: version.Info{Major:"1", Minor:"4", GitVersion:"v1.4.6+e569a27", GitCommit:"e569a27d02001e343cb68086bc06d47804f62af6", GitTreeState:"not a git tree", BuildDate:"2016-11-12T09:25:15Z", GoVersion:"go1.7.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"2", GitVersion:"v1.2.0", GitCommit:"5cb86ee022267586db386f62781338b0483733b3", GitTreeState:"clean", BuildDate:"", GoVersion:"", Compiler:"", Platform:""}

I have opened the docker-machine security-group inbound port 80.

The container is accessible inside the vpc, but not from outside like curl/browser

cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro/cluster on master [!]
$ curl $(kmachine ip cescoferraro)
curl: (28) Connection timed out after 60913 milliseconds
cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro/cluster on master [!]
$ kmachine ssh cescoferraro
Welcome to Ubuntu 14.04.5 LTS (GNU/Linux 3.13.0-106-generic x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Mon Jan  9 18:40:40 UTC 2017

  System load:  0.0                Processes:              126
  Usage of /:   17.4% of 15.61GB   Users logged in:        0
  Memory usage: 33%                IP address for eth0:    172.31.2.52
  Swap usage:   0%                 IP address for docker0: 172.17.0.1

  Graph this data and manage this system at:
    https://landscape.canonical.com/

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud


Last login: Mon Jan  9 18:40:41 2017 from 179.219.205.224
ubuntu@cescoferraro:~$ curl 127.0.0.1
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.11.3</center>
</body>
</html>
ubuntu@cescoferraro:~$ logout
cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro/cluster/dashboard on master [!]
$ k get pods
NAME                                        READY     STATUS    RESTARTS   AGE
cescoferraro-cescoferraro                   5/5       Running   0          24m
default-http-backend-gd8sw                  1/1       Running   0          20m
nginx-ingress-controller-2698042824-ifpna   1/1       Running   1          20m

when using machine to create a virtual box VM using boot2k8s, machine reports using a token for auth, but boot2k8s does not use one.

Also 8080 is forwarded to a random port created by machine, which is not the port reported by the commands/env.go

@cab105 could you look at my latest commit.

We need to update Godeps properly. I switched to "k8s.io/helm/pkg/kube"
in commands/deploy.go

thanks

just because, it's not docker-machine

I did a clean install and followed the instructions to create a Kmachine, but cannot connect, even after allowing a few minutes to start everything.

$ kmachine create -d virtualbox publiccloud
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring kubernetes...
Copying certs to the remote system...
To see how to connect Docker to this machine, run: kmachine env publiccloud
$ kmachine env publiccloud
kubectl config set-cluster publiccloud --server=https://192.168.99.101:6443 --insecure-skip-tls-verify=false
kubectl config set-cluster publiccloud --server=https://192.168.99.101:6443 --certificate-authority=/Users/alexknol/.kube/machine/machines/publiccloud/ca.pem
kubectl config set-credentials publiccloud --token=1dylmUdE73QhkPi3pF6peTNjI7z3hWqo
kubectl config set-context publiccloud --user=publiccloud --cluster=publiccloud
kubectl config use-context publiccloud
export DOCKER_TLS_VERIFY="1"
export DOCKER_HOST="tcp://192.168.99.101:2376"
export DOCKER_CERT_PATH="/Users/alexknol/.kube/machine/machines/publiccloud"
export DOCKER_MACHINE_NAME="publiccloud"
# Run this command to configure your shell:
# eval "$(kmachine env publiccloud)"
$ eval "$(kmachine env publiccloud)"
cluster "publiccloud" set.
cluster "publiccloud" set.
user "publiccloud" set.
context "publiccloud" set.
switched to context "publiccloud".
$ kubectl get pods
error: couldn't read version from server: Get https://192.168.99.101:6443/api: dial tcp 192.168.99.101:6443: connection refused
$ kubectl get pods
error: couldn't read version from server: Get https://192.168.99.101:6443/api: dial tcp 192.168.99.101:6443: connection refused

To be able to access our private registry over I need to add a .dockercfg in /var/lib/kubelet/ this however gets wiped on every restart of the VM. I am using VirtualBox...

Is there any way we can make this persist?

"make cross" works, but

TARGET_OS="linux" TARGET_ARCH="amd64" make

fails with:

commands/commands.go
commands/create.go
commands/deploy.go
commands/env.go
commands/ls.go
drivers/amazonec2/amazonec2.go
drivers/virtualbox/virtualbox.go
drivers/vmwarefusion/fusion.go
libmachine/drivers/base.go
libmachine/host/host.go
libmachine/kubernetes/kubernetes.go
libmachine/provision/arch.go
libmachine/provision/boot2docker.go
libmachine/provision/configure_kubernetes.go
libmachine/provision/coreos.go
libmachine/provision/debian.go
libmachine/provision/generic.go
libmachine/provision/provisioner.go
libmachine/provision/rancheros.go
libmachine/provision/redhat.go
libmachine/provision/suse.go
libmachine/provision/ubuntu.go
version/version.go
make: *** [fmt] Error 1
mk/validate.mk:13: recipe for target 'fmt' failed
Makefile:18: recipe for target 'test' failed
make: *** [test] Error 2

I was asking myself on the differences between your kmachine and the docker-toolbox project.

What are the differences with :

install docker-toolbox
start a kubernetes node using the docker version
connect to it

and your installation ?
Is it all the automated deployment on all the provider ?

Sorry, don't feel attacked by this question, I just want to understand ...

There seems to be a permission issue during the provisioning

$ docker-machine create -d amazonec2 kubeconaws1
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Copying certs to the remote system...
Error creating machine: Error running provisioning: Something went wrong running an SSH command!
command : mkdir -p /var/run/kubernetes
err : exit status 1
output : mkdir: cannot create directory ‘/var/run/kubernetes’: Permission denied

README

Deploy Addons

You can deploy the DNS and Dashboard Add-ons with:

$ kmachine deploy dns <machine_name>
$ kmachine deploy dashboard <machine_name>

cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro/spotify on master [+!$]
$ kmachine deploy dashboard cescoferraro.xyz
Host "dashboard" does not exist
cescoferraro@mint-pro: ~/code/go/src/github.com/cescoferraro/spotify on master [+!$]
$ kmachine deploy cescoferraro.xyz dashboard
using host: https://52.67.226.149:6443
######################################################################
# Copyright 2015 The Kubernetes Authors All rights reserved.
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#     http://www.apache.org/licenses/LICENSE-2.0
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
######################################################################
....

Hi,

Just taking km 0.5.0 out for a spin. I have a successful pure k8s aws deploy and trying out km locally reusing my k8s recipes. Having issue linking up to services. Think it's a known issue but wanted to check status/reason why this does not seem to work.

Case and point. I have a cassandra pod and service. Launch a virtualbox vm and try to access my cqlsh in my pod using cassandra service. Works with pure k8s 1.2.0a8 but fail with Name or service not known on km 0.5.0.

ku describe svc cassandra - shows the endpoint is correctly assigned and cqlsh command works with the ips but not the service name as expected.

Thank you!

currently the context is hardcoded to user/cluster kmachine.
We need to use the machine name given via stdin to create multiple contexts ...kmachine-<machine_name>

Just modify the way we write the env config.

We need to add windows (powershell) support for the kmachine env command.

we probably want to download boot2k8s.iso specifically, in case there is an existing boot2dock.iso on the system,...or will it provision k8s on this existing boot2docker image ?

etcd data is not persisted, as a result all the cluster config is lost as soon as Docker is restarted. This is an issue when the user wants to reconfigure the Docker daemon.

It would be nice if the Kubernetes version was not tied to the version of kmachine

For example, if I wanted to try the latest alpha build of 1.3, or use some previous version.

Perhaps a command line flag when the machine is built?

I tried kmachine with exoscale driver on MacBookAir (OSX 10.10.1).

I checked out the repository and build kmachine using make build and followed the steps of your blog to create a machine. The machine was created successfully.

$ export EXOSCALE_API_KEY=<MY_API_KEY>
$ export EXOSCALE_API_SECRET=<MY_SECRET_KEY>

$ ./kmachine_darwin-amd64 create -d exoscale foobar
Querying exoscale for the requested parameters...
Security group docker-machine does not exist, create it
Generate an SSH keypair...
Spawn exoscale host...
Waiting for job to complete...
To see how to connect Docker to this machine, run: kmachine_darwin-amd64 env foobar

But kmachine env command raises following error.

$ ./kmachine_darwin-amd64 env foobar
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1
Error getting SSH command to check if the daemon is up: exit status 1

Docker daemon was not running in the machine as below.

$ ./kmachine_darwin-amd64 ssh foobar
$ sudo docker version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): linux/amd64
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?

I also tried docker machine v0.3.0 exoscale driver. It could create a machine and provision docker daemon successfully.

What can I do to provision the machine properly?

Config

export AWS_ACCESS_KEY_ID="AKIAI...."
export AWS_SECRET_ACCESS_KEY="AL3QOfiVo5FT70pi...."
export AWS_DEFAULT_REGION="sa-east-1"
export AWS_VPC_ID="i-09...."
export DIGITALOCEAN_ACCESS_TOKEN="25..........76"

Digital Ocean works

cesco@laptop: ~/code/go/src/bitbucket.org/cescoferraro
$ kmachine create -d digitalocean skippbox
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Rebooting system...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring kubernetes...
Copying certs to the remote system...
To see how to connect Docker to this machine, run: kmachine env skippbox

I am having issues with setting the right zone at aws.

cesco@laptop: ~/code/go/src/bitbucket.org/cescoferraro
$ echo $AWS_DEFAULT_REGION

cesco@laptop: ~/code/go/src/bitbucket.org/cescoferraro
$ kmachine create -d amazonec2 aws
Running pre-create checks...
Error creating machine: Error with pre-create check: unable to find a subnet in the zone: us-east-1a
cesco@laptop: ~/code/go/src/bitbucket.org/cescoferraro
$ . ~/.bash.local
cesco@laptop: ~/code/go/src/bitbucket.org/cescoferraro
$ echo $AWS_DEFAULT_REGION
sa-east-1
cesco@laptop: ~/code/go/src/bitbucket.org/cescoferraro
$ kmachine create -d amazonec2 aws
Running pre-create checks...
Error creating machine: Error with pre-create check: unable to find a subnet in the zone: sa-east-1a

Instead of using the hard coded 'abcdefghijkl" token I put in for test, we need to generate a proper random token.

https://github.com/kubernetes/kubernetes/blob/master/docs/admin/authentication.md

Considering the many issues with running the kubelet in a container, we might consider running it as a service like for virtualbox.

libmachine/provision/utils.go runs is as a container...

With the boto2docker image there is indeed an issue with the startup script.

I tried to use the boot2k8s image, it work'ish:

$ PATH=$PWD:$PATH ./docker-machine create -d virtualbox --virtualbox-boot2docker-url=https://github.com/skippbox/boot2k8s/releases/download/v1.0.3/boot2k8s.iso yoyo
Running pre-create checks...
Creating machine...
Waiting for machine to be running, this may take a few minutes...
Machine is running, waiting for SSH to be available...
Detecting operating system of created instance...
Provisioning created instance...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring kubernetes...
Error creating machine: Error running provisioning: Something went wrong running an SSH command!
command : sudo /etc/rc.d/k8s.sh
err : exit status 255
output : W1102 12:42:28.728005 2302 server.go:474] Could not load kubeconfig file /var/lib/kubelet/kubeconfig: stat /var/lib/kubelet/kubeconfig: no such file or directory. Trying auth path instead.
W1102 12:42:28.728347 2302 server.go:436] Could not load kubernetes auth path /var/lib/kubelet/kubernetes_auth: stat /var/lib/kubelet/kubernetes_auth: no such file or directory. Continuing with defaults.
I1102 12:42:28.729008 2302 server.go:273] Using root directory: /var/lib/kubelet
I1102 12:42:28.729390 2302 manager.go:127] cAdvisor running in container: "/"
I1102 12:42:28.730203 2302 fs.go:93] Filesystem partitions: map[/dev/sda1:{mountpoint:/mnt/sda1 major:8 minor:1}]
I1102 12:42:28.731747 2302 machine.go:229] Couldn't collect info from any of the files in "/etc/machine-id,/var/lib/dbus/machine-id"
I1102 12:42:28.732105 2302 manager.go:156] Machine: {NumCores:1 CpuFrequency:2294770 MemoryCapacity:1044578304 MachineID: SystemUUID:173A5A3B-770A-49E7-952A-0052791EA18F BootID:89d1fe0f-631c-4030-93ac-f167825dbb6c Filesystems:[{Device:/dev/sda1 Capacity:19507089408}] DiskMap:map[250:0:{Name:zram0 Major:250 Minor:0 Size:214212608 Scheduler:none} 8:0:{Name:sda Major:8 Minor:0 Size:20971520000 Scheduler:deadline}] NetworkDevices:[{Name:dummy0 MacAddress:2a:9b:d4:76:01:8e Speed:0 Mtu:1500} {Name:eth0 MacAddress:08:00:27:87:d4:a3 Speed:1000 Mtu:1500} {Name:eth1 MacAddress:08:00:27:ac:00:5e Speed:1000 Mtu:1500}] Topology:[{Id:0 Memory:0 Cores:[{Id:0 Threads:[0] Caches:[{Size:32768 Type:Data Level:1} {Size:32768 Type:Instruction Level:1} {Size:262144 Type:Unified Level:2}]}] Caches:[{Size:3145728 Type:Unified Level:3}]}]}
I1102 12:42:28.733142 2302 manager.go:163] Version: {KernelVersion:4.1.12-boot2docker ContainerOsVersion:Boot2Docker 1.8.3 (TCL 6.4); master : 9f3803e - Tue Oct 27 17:31:31 UTC 2015 DockerVersion:1.8.3 CadvisorVersion:0.15.1}
I1102 12:42:28.739199 2302 plugins.go:69] No cloud provider specified.
I1102 12:42:28.739871 2302 server.go:292] Successfully initialized cloud provider: "" from the config file: ""
I1102 12:42:28.739829 2302 cadvisor_linux.go:99] Failed to register cAdvisor on port 4194, retrying. Error: listen tcp :4194: bind: address already in use
I1102 12:42:29.780317 2302 docker.go:295] Connecting to docker on unix:///var/run/docker.sock
I1102 12:42:29.783334 2302 server.go:663] Adding manifest file: /usr/local/etc/kubernetes/manifests
I1102 12:42:29.783630 2302 file.go:47] Watching path "/usr/local/etc/kubernetes/manifests"
I1102 12:42:29.783831 2302 server.go:673] Watching apiserver
I1102 12:42:29.791501 2302 manager.go:158] Setting dockerRoot to /mnt/sda1/var/lib/docker
E1102 12:42:29.810190 2302 reflector.go:136] Failed to list *api.Node: Get http://127.0.0.1:8080/api/v1/nodes?fieldSelector=metadata.name%3Dyoyo: dial tcp 127.0.0.1:8080: connection refused
E1102 12:42:29.810782 2302 reflector.go:136] Failed to list *api.Service: Get http://127.0.0.1:8080/api/v1/services: dial tcp 127.0.0.1:8080: connection refused
E1102 12:42:29.810879 2302 reflector.go:136] Failed to list *api.Pod: Get http://127.0.0.1:8080/api/v1/pods?fieldSelector=spec.nodeName%3Dyoyo: dial tcp 127.0.0.1:8080: connection refused
I1102 12:42:29.934139 2302 plugins.go:56] Registering credential provider: .dockercfg
I1102 12:42:29.934597 2302 container_manager_linux.go:100] Configure resource-only container /docker-daemon with memory limit: 731204812
I1102 12:42:29.935882 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/aws-ebs"
I1102 12:42:29.936224 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/empty-dir"
I1102 12:42:29.936449 2302 plugins.go:180] Loaded volume plugin "empty"
I1102 12:42:29.936678 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/gce-pd"
I1102 12:42:29.936891 2302 plugins.go:180] Loaded volume plugin "gce-pd"
I1102 12:42:29.937149 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/git-repo"
I1102 12:42:29.937363 2302 plugins.go:180] Loaded volume plugin "git"
I1102 12:42:29.937573 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/host-path"
I1102 12:42:29.937795 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/nfs"
I1102 12:42:29.938004 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/secret"
I1102 12:42:29.938217 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/iscsi"
I1102 12:42:29.938459 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/glusterfs"
I1102 12:42:29.938713 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/persistent-claim"
I1102 12:42:29.939011 2302 plugins.go:180] Loaded volume plugin "kubernetes.io/rbd"
I1102 12:42:29.939052 2302 server.go:635] Started kubelet
E1102 12:42:29.940298 2302 kubelet.go:682] Image garbage collection failed: unable to find data for container /
I1102 12:42:29.945422 2302 kubelet.go:702] Running in container "/kubelet"
I1102 12:42:29.951374 2302 factory.go:234] Registering Docker factory
I1102 12:42:29.952258 2302 factory.go:89] Registering Raw factory
I1102 12:42:29.953993 2302 manager.go:946] Started watching for new ooms in manager
W1102 12:42:29.954412 2302 manager.go:230] Could not configure a source for OOM detection, disabling OOM events: exec: "journalctl": executable file not found in $PATH
I1102 12:42:29.955190 2302 manager.go:243] Starting recovery of all containers
I1102 12:42:29.957856 2302 manager.go:248] Recovery completed
I1102 12:42:29.958869 2302 server.go:63] Starting to listen on 0.0.0.0:10250
I1102 12:42:29.959208 2302 server.go:82] Starting to listen read-only on 0.0.0.0:10255
I1102 12:42:29.964840 2302 status_manager.go:76] Starting to sync pod status with apiserver
I1102 12:42:29.965166 2302 kubelet.go:1725] Starting kubelet main sync loop.
E1102 12:42:29.965527 2302 event.go:194] Unable to write event: 'Post http://127.0.0.1:8080/api/v1/namespaces/default/events: dial tcp 127.0.0.1:8080: connection refused' (may retry after sleeping)
E1102 12:42:29.959284 2302 server.go:391] Starting health server failed: listen tcp 127.0.0.1:10248: bind: address already in use
E1102 12:42:29.990280 2302 kubelet.go:1641] error getting node: node yoyo not found
I1102 12:42:29.991750 2302 manager.go:1384] Need to restart pod infra container for "kube-controller-yoyo_default" because it is not found
W1102 12:42:29.994014 2302 status_manager.go:80] Failed to updated pod status: error updating status for pod "kube-controller-yoyo_default": Get http://127.0.0.1:8080/api/v1/namespaces/default/pods/kube-controller-yoyo: dial tcp 127.0.0.1:8080: connection refused
F1102 12:42:29.994463 2302 server.go:93] listen tcp 0.0.0.0:10255: bind: address already in use

It errors out, but does the job ....

Need to make sure it works without errors.

boot2k8s release is on v1.1.4 but somehow when doing:
kmachine create -d virtualbox foobar
the resulting machine is on v1.1.2

I cleared my cache and the manifests on kmachine that should be put in place on boot2k8s are also on v1.1.4.

A little mystery here :)

Is there a way to use this w/ existing docker machine? (e.g., I just want to run k8s on single node docker machine :D)

Thanks,

Setup TLS connection for k8s endpoint.
We could re-use the certs generated for the docker auth.

The guide from Kelsey Hightower is very nice and good reference:
https://github.com/kelseyhightower/docker-kubernetes-tls-guide