TipsAndTricks/DockerOnImage - Revision history

Bavery: /* Current Hacks Needed */

2017-07-14T19:54:25Z

Current Hacks Needed

← Older revision		Revision as of 19:54, 14 July 2017
Line 50:		Line 50:
	== Current Hacks Needed ==		== Current Hacks Needed ==
	Some of this is not upstreamed yet, so here's some patches you may need to apply. Check and see of they have been accepted upstream or not, first...		Some of this is not upstreamed yet, so here's some patches you may need to apply. Check and see of they have been accepted upstream or not, first...
	~~=== Additional kernel module needed for docker ===~~
	~~See [[https://lists.yoctoproject.org/pipermail/meta-virtualization/2017-July/002625.html mailing list patch]]. This adds a kernel config module NETFILTER_XT_MATCH_ADDRTYPE so it can start up.~~
	=== Proxy problems ===		=== Proxy problems ===
	Once on the target board, you need to tell docker about your proxy (if you have one). This is a little hard to do by hand, so here are a couple of files you can insert into meta-virtualization to help you along.		Once on the target board, you need to tell docker about your proxy (if you have one). This is a little hard to do by hand, so here are a couple of files you can insert into meta-virtualization to help you along.

2017-07-07T23:57:55Z

← Older revision		Revision as of 23:57, 7 July 2017
Line 135:		Line 135:
	$ docker run -it --rm busybox sh		$ docker run -it --rm busybox sh
	/ #		/ #
			If there are issues try <code> systemctl status docker </code> to see what went wrong.

2017-07-07T23:57:24Z

← Older revision		Revision as of 23:57, 7 July 2017
Line 126:		Line 126:
	Live Restore Enabled: false		Live Restore Enabled: false

	~~$ systemctl docker status~~
	$ docker pull busybox		$ docker pull busybox
			Using default tag: latest
			latest: Pulling from library/busybox
			27144aa8f1b9: Pull complete
			Digest: sha256:be3c11fdba7cfe299214e46edc642e09514dbb9bbefcd0d3836c05a1e0cd0642
			Status: Downloaded newer image for busybox:latest

	$ docker run -it --rm busybox sh		$ docker run -it --rm busybox sh
			/ #

2017-07-07T23:55:35Z

How to Test

← Older revision		Revision as of 23:55, 7 July 2017
Line 117:		Line 117:
	Debug Mode (client): false		Debug Mode (client): false
	Debug Mode (server): false		Debug Mode (server): false
	Http Proxy: http://~~proxy-chain.intel~~.com:~~911~~/		Http Proxy: http://foo.com:123/
	Registry: https://index.docker.io/v1/		Registry: https://index.docker.io/v1/
	WARNING: No cpu cfs quota support		WARNING: No cpu cfs quota support

2017-07-07T23:54:57Z

@@ Line 1: / Line 1: @@
-This assumes you'd like to build an image that supports docker on a YP image.  This is pretty straightforward due to the great work done  on the meta-virtualization layer, mostly by people at Wind River.  This document will show how to get docker running on a Minnowboard (Turbot).  Note, these layers change, so this is accurate as of July 2017.
+This assumes you'd like to build an image that supports docker on a YP image.  This is pretty straightforward due to the great work done  on the meta-virtualization layer, mostly by people at Wind River.  This document will show how to get docker running on a Nuc. I have run  the same image on a  Minnowboard (Turbot) successfully as well.  Note, these layers change, so this is accurate as of July 2017.
 == What Layers Do You Need? ==
 The main layer is meta-virtualization. This can be found using the layers.openembedded search app, Here's the [[https://layers.openembedded.org/layerindex/branch/master/layer/meta-virtualization/ meta-virtualiation]]  entry. As you can see from the dependency list, this layer requires oe-core,meta-oe, meta-networking, and meta-filesystems. Some of these (like meta-networking) have additional dependencies. Here's the complete list of additional layers you need:
@@ Line 84: / Line 84: @@
 *** sudo chmod 666 /dev/sdX
 *** oe-run-native bmap-tools-native bmaptool copy ./tmp/deploy/images/genericx86-64/core-image-base-genericx86-64.wic  /dev/sdX

2017-07-07T23:46:25Z

← Older revision		Revision as of 23:46, 7 July 2017
Line 75:		Line 75:
	Once these are all in place, you are ready to make your image. I'd suggest building core-image-base. <strong> Note: core-image-mininal will NOT work since it does not include the kernel module packages by default.</strong>		Once these are all in place, you are ready to make your image. I'd suggest building core-image-base. <strong> Note: core-image-mininal will NOT work since it does not include the kernel module packages by default.</strong>
	$bitbake core-image-base		$bitbake core-image-base
	=== How to get the image onto your usb key ===		== How to get the image onto your usb key ==
	You need to check (lsusb or dmesg) to see that /dev/sdX your usb key showed up as.		You need to check (lsusb or dmesg) to see that /dev/sdX your usb key showed up as.
	* sudo umount /dev/sdX1;sudo umount /dev/sdX2; <unmount any others as well>		* sudo umount /dev/sdX1;sudo umount /dev/sdX2; <unmount any others as well>

2017-07-07T23:45:48Z

← Older revision		Revision as of 23:45, 7 July 2017
Line 74:		Line 74:
	== What To Build ==		== What To Build ==
	Once these are all in place, you are ready to make your image. I'd suggest building core-image-base. <strong> Note: core-image-mininal will NOT work since it does not include the kernel module packages by default.</strong>		Once these are all in place, you are ready to make your image. I'd suggest building core-image-base. <strong> Note: core-image-mininal will NOT work since it does not include the kernel module packages by default.</strong>
			$bitbake core-image-base
			=== How to get the image onto your usb key ===
			You need to check (lsusb or dmesg) to see that /dev/sdX your usb key showed up as.
			* sudo umount /dev/sdX1;sudo umount /dev/sdX2; <unmount any others as well>
			** slow way
			*** sudo dd if=tmp/deploy/images/genericx86-64/core-image-base-genericx86-64.wic of=/dev/sdX
			** fast way
			*** bitbake bmap-tools-native -caddto_recipe_sysroot
			*** sudo chmod 666 /dev/sdX
			*** oe-run-native bmap-tools-native bmaptool copy ./tmp/deploy/images/genericx86-64/core-image-base-genericx86-64.wic /dev/sdX

2017-07-07T23:41:37Z

← Older revision		Revision as of 23:41, 7 July 2017
Line 71:		Line 71:
	[Service]		[Service]
	Environment="HTTP_PROXY={URL}/"		Environment="HTTP_PROXY={URL}/"

			== What To Build ==
			Once these are all in place, you are ready to make your image. I'd suggest building core-image-base. <strong> Note: core-image-mininal will NOT work since it does not include the kernel module packages by default.</strong>

2017-07-07T23:40:04Z

Proxy problems

← Older revision		Revision as of 23:40, 7 July 2017
Line 57:		Line 57:
	meta-virtualization$ cat recipes-containers/docker/docker_git.bbappend		meta-virtualization$ cat recipes-containers/docker/docker_git.bbappend


	SRC_URI += "file://http-proxy.conf"		SRC_URI += "file://http-proxy.conf"
	do_install_append() {		do_install_append() {

2017-07-07T23:39:50Z

← Older revision		Revision as of 23:39, 7 July 2017
Line 54:		Line 54:
	=== Proxy problems ===		=== Proxy problems ===
	Once on the target board, you need to tell docker about your proxy (if you have one). This is a little hard to do by hand, so here are a couple of files you can insert into meta-virtualization to help you along.		Once on the target board, you need to tell docker about your proxy (if you have one). This is a little hard to do by hand, so here are a couple of files you can insert into meta-virtualization to help you along.

	meta-virtualization$ cat recipes-containers/docker/docker_git.bbappend		meta-virtualization$ cat recipes-containers/docker/docker_git.bbappend