Issue 1:
W0921 21:05:38.642280 11417 docker.go:265] found a container with the "k8s" prefix, but too few fields (2): "k8s_unidentified"
I0921 21:05:38.642486 11417 container_gc.go:140] Removing unidentified dead container "/k8s_unidentified" with ID "2876"
I0921 21:05:38.642860 11417 disk_manager.go:114] Running out of space on disk for "root": available 0 MB, threshold 250 MB
I0921 21:05:38.642971 11417 disk_manager.go:114] Running out of space on disk for "docker": available 1 MB, threshold 250 MB
I0921 21:05:38.643086 11417 disk_manager.go:114] Running out of space on disk for "root": available 9 MB, threshold 10 MB
I0921 21:05:38.643267 11417 disk_manager.go:114] Running out of space on disk for "root": available 9 MB, threshold 10 MB
I0921 21:05:38.643675 11417 image_manager.go:255] [ImageManager]: Removing image "image-0" to free 1024 bytes
I0921 21:05:38.643804 11417 image_manager.go:255] [ImageManager]: Removing image "image-0" to free 1024 bytes
I0921 21:05:38.643927 11417 image_manager.go:255] [ImageManager]: Removing image "image-0" to free 1024 bytes
I0921 21:05:38.644042 11417 image_manager.go:255] [ImageManager]: Removing image "image-0" to free 1024 bytes
I0921 21:05:38.644185 11417 image_manager.go:203] [ImageManager]: Disk usage on "" () is at 95% which is over the high threshold (90%). Trying to free 150 bytes
I0921 21:05:38.644229 11417 image_manager.go:255] [ImageManager]: Removing image "image-0" to free 450 bytes
I0921 21:05:38.644305 11417 image_manager.go:203] [ImageManager]: Disk usage on "" () is at 95% which is over the high threshold (90%). Trying to free 150 bytes
I0921 21:05:38.644337 11417 image_manager.go:255] [ImageManager]: Removing image "image-0" to free 50 bytes
W0921 21:05:38.646950 11417 kubelet.go:586] Data dir for pod "bothpod" exists in both old and new form, using new
W0921 21:05:38.647292 11417 kubelet.go:637] Data dir for pod "newpod", container "bothctr" exists in both old and new form, using new
--- FAIL: TestSyncLoopAbort-2 (0.00s)
kubelet_test.go:346: expected syncLoopIteration to return !ok since update chan was closed
E0921 21:05:38.663308 11417 kubelet.go:1609] Pod "_": HostPort is already allocated, ignoring: [[0].port: duplicate value '81/']
E0921 21:05:38.664016 11417 kubelet.go:1609] Pod "newpod_foo": HostPort is already allocated, ignoring: [[0].port: duplicate value '80/']
E0921 21:05:38.667189 11417 kubelet.go:1609] Pod "pod2_": HostPort is already allocated, ignoring: [[0].port: duplicate value '80/']
E0921 21:05:38.669280 11417 kubelet.go:1201] Deleting mirror pod "foo_ns" because it is outdated
W0921 21:05:38.673735 11417 kubelet.go:781] Port name conflicted, "fooContainer-foo" is defined more than once
W0921 21:05:38.673801 11417 kubelet.go:781] Port name conflicted, "fooContainer-TCP:80" is defined more than once
E0921 21:05:38.684049 11417 node_manager.go:478] Error updating node status, will retry: error getting node "127.0.0.1": Node "127.0.0.1" not found
E0921 21:05:38.684109 11417 node_manager.go:478] Error updating node status, will retry: error getting node "127.0.0.1": Node "127.0.0.1" not found
E0921 21:05:38.684211 11417 node_manager.go:478] Error updating node status, will retry: error getting node "127.0.0.1": Node "127.0.0.1" not found
E0921 21:05:38.684248 11417 node_manager.go:478] Error updating node status, will retry: error getting node "127.0.0.1": Node "127.0.0.1" not found
E0921 21:05:38.684286 11417 node_manager.go:478] Error updating node status, will retry: error getting node "127.0.0.1": Node "127.0.0.1" not found
I0921 21:05:38.784666 11417 node_manager.go:279] Node 127.0.0.1 was previously registered
I0921 21:05:38.784849 11417 plugins.go:56] Registering credential provider: .dockercfg
I0921 21:05:38.835534 11417 plugins.go:56] Registering credential provider: .dockercfg
I0921 21:05:38.835691 11417 plugins.go:56] Registering credential provider: .dockercfg
I0921 21:05:38.886180 11417 plugins.go:56] Registering credential provider: .dockercfg
W0921 21:05:38.886326 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_foo_new_12345678_0"
W0921 21:05:38.886347 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_foo_new_12345678_0"
W0921 21:05:38.886361 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886374 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886413 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_foo_new_12345678_0"
W0921 21:05:38.886453 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_foo_new_12345678_0"
W0921 21:05:38.886467 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886479 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886524 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_98765_0"
W0921 21:05:38.886539 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_98765_0"
W0921 21:05:38.886553 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886564 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886594 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886631 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886644 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_98765_0"
W0921 21:05:38.886655 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_98765_0"
W0921 21:05:38.886693 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_12345678_0"
W0921 21:05:38.886707 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_12345678_0"
W0921 21:05:38.886718 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886729 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886749 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_12345678_0"
W0921 21:05:38.886760 11417 docker.go:275] invalid container hash "hash123" in container "k8s_bar.hash123_bar_new_12345678_0"
W0921 21:05:38.886772 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
W0921 21:05:38.886782 11417 docker.go:275] invalid container hash "hash123" in container "k8s_POD.hash123_foo_new_12345678_0"
I0921 21:05:38.887038 11417 plugins.go:56] Registering credential provider: .dockercfg
I0921 21:05:38.887099 11417 runonce.go:71] waiting for 1 pods
I0921 21:05:38.887227 11417 runonce.go:135] Container "bar" not running: api.ContainerState{Waiting:(*api.ContainerStateWaiting)(0xc2081e9f80), Running:(*api.ContainerStateRunning)(nil), Terminated:(*api.ContainerStateTerminated)(nil)}
I0921 21:05:38.887250 11417 runonce.go:109] pod "foo" containers not running: syncing
E0921 21:05:38.887882 11417 manager.go:1491] DNS ResolvConfPath is empty.
I0921 21:05:38.888079 11417 hairpin.go:49] Unable to find pair interface, setting up all interfaces: exec: "nsenter": executable file not found in $PATH
W0921 21:05:38.891155 11417 docker.go:265] found a container with the "k8s" prefix, but too few fields (5): "k8s_net_foo.new.test_abcdefgh_42"
I0921 21:05:38.891249 11417 runonce.go:119] pod "foo" containers synced, waiting for 1ms
W0921 21:05:38.892523 11417 docker.go:265] found a container with the "k8s" prefix, but too few fields (5): "k8s_net_foo.new.test_abcdefgh_42"
E0921 21:05:38.892555 11417 manager.go:859] Error examining the container: parse docker container name "/k8s_net_foo.new.test_abcdefgh_42" error: Docker container name "k8s_net_foo.new.test_abcdefgh_42" has less parts than expected [k8s net foo.new.test abcdefgh 42]
W0921 21:05:38.892673 11417 docker.go:265] found a container with the "k8s" prefix, but too few fields (5): "k8s_net_foo.new.test_abcdefgh_42"
I0921 21:05:38.892701 11417 runonce.go:106] pod "foo" containers running
I0921 21:05:38.892717 11417 runonce.go:81] started pod "foo"
I0921 21:05:38.892753 11417 runonce.go:87] 1 pods started
W0921 21:05:39.253084 11417 connection.go:126] Stream rejected: Unable to parse '' as a port: strconv.ParseUint: parsing "": invalid syntax
W0921 21:05:39.257265 11417 connection.go:126] Stream rejected: Unable to parse 'abc' as a port: strconv.ParseUint: parsing "abc": invalid syntax
W0921 21:05:39.273529 11417 connection.go:126] Stream rejected: Unable to parse '-1' as a port: strconv.ParseUint: parsing "-1": invalid syntax
W0921 21:05:39.277341 11417 connection.go:126] Stream rejected: Unable to parse '65536' as a port: strconv.ParseUint: parsing "65536": value out of range
W0921 21:05:39.281039 11417 connection.go:126] Stream rejected: Port '0' must be greater than 0
FAIL

Issue 2:
Hi!

$ ./cluster/kube-up.sh
... Starting cluster using provider: vagrant
... calling verify-prereqs
... calling kube-up
Bringing machine 'master' up with 'virtualbox' provider...
Bringing machine 'node-1' up with 'virtualbox' provider...
==> master: Importing base box 'kube-fedora23'...
==> master: Matching MAC address for NAT networking...
==> master: Setting the name of the VM: kubernetes_master_1465131057159_61370
==> master: Fixed port collision for 22 => 2222. Now on port 2200.
==> master: Clearing any previously set network interfaces...
==> master: Preparing network interfaces based on configuration...
master: Adapter 1: nat
master: Adapter 2: hostonly
==> master: Forwarding ports...
master: 22 (guest) => 2200 (host) (adapter 1)
==> master: Running 'pre-boot' VM customizations...
==> master: Booting VM...
==> master: Waiting for machine to boot. This may take a few minutes...
master: SSH address: 127.0.0.1:2200
master: SSH username: vagrant
master: SSH auth method: private key
master:
master: Vagrant insecure key detected. Vagrant will automatically replace
master: this with a newly generated keypair for better security.
master:
master: Inserting generated public key within guest...
master: Removing insecure key from the guest if it's present...
master: Key inserted! Disconnecting and reconnecting using new SSH key...
==> master: Machine booted and ready!
==> master: Checking for guest additions in VM...
==> master: Configuring and enabling network interfaces...
==> master: Exporting NFS shared folders...
==> master: Preparing to edit /etc/exports. Administrator privileges will be required...
● nfs-server.service - NFS server and services
Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2016-06-03 07:44:24 EDT; 2 days ago
Main PID: 1029 (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CPU: 0
CGroup: /system.slice/nfs-server.service

Jun 03 07:44:24 Monster systemd[1]: Starting NFS server and services...
Jun 03 07:44:24 Monster systemd[1]: Started NFS server and services.
exportfs: duplicated export entries:
exportfs: 10.245.1.2:/mnt/linux-data/Code/Code9/kubernetes
exportfs: 10.245.1.2:/mnt/linux-data/Code/Code9/kubernetes
==> master: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o 'vers=3,udp' 10.245.1.1:'/mnt/linux-data/Code/Code9/kubernetes' /vagrant

Stdout from the command:

mount.nfs: access denied by server while mounting 10.245.1.1:/mnt/linux-data/Code/Code9/kubernetes

Stderr from the command:

I have already entered my password for sudo rights in that terminal in the last few minutes, but the first time I tried the command it asked me for my password.