TipsAndTricks/CropsCLIContainers - Revision history

PaulEggleton: Fix dockerhub URL

2018-01-30T03:26:21Z

Fix dockerhub URL

← Older revision		Revision as of 03:26, 30 January 2018
Line 2:		Line 2:
	== Introduction ==		== Introduction ==
	CROPS provides CLI containers that allow you to run the set of tools listed in the title on Mac OSX, Windows or Linux.		CROPS provides CLI containers that allow you to run the set of tools listed in the title on Mac OSX, Windows or Linux.
	The containers themselves are available on Dockerhub at https://hub.docker.com/u/crops~~/dashboard~~/		The containers themselves are available on Dockerhub at https://hub.docker.com/u/crops/

	You may wonder why you would use these containers on Linux. The main reason is it gives you a guaranteed clean environment from which to build. Also it means you don't need to install the dependent packages required by the build tools. Measurements show '''no''' speed degradation when running in the container. This wiki assumes you have followed the basic documentation on the CROPS github Readme's (like https://github.com/crops/poky-container) and are looking for more tips.		You may wonder why you would use these containers on Linux. The main reason is it gives you a guaranteed clean environment from which to build. Also it means you don't need to install the dependent packages required by the build tools. Measurements show '''no''' speed degradation when running in the container. This wiki assumes you have followed the basic documentation on the CROPS github Readme's (like https://github.com/crops/poky-container) and are looking for more tips.

Bavery at 22:25, 29 August 2017

2017-08-29T22:25:12Z

← Older revision		Revision as of 22:25, 29 August 2017
Line 51:		Line 51:
	devtool find-recipe busybox		devtool find-recipe busybox
	this can make cutting and pasting easier from the "in container terminal" which lacks an editor into the editor or terminal with an editor on the host system.		this can make cutting and pasting easier from the "in container terminal" which lacks an editor into the editor or terminal with an editor on the host system.
			== Workflow ==
			I tend to run this under tmux. I keep one tmux panel inside the container for commands and another outside the container to do host side editing/git operations.
			== Git issues ==
			Sometimes i try to do something in the container like git stash save "my stash" and it fails telling me that pokyuser does not have a default git user or email setup. There are 2 ways to work around this.

Bavery at 21:01, 29 August 2017

2017-08-29T21:01:47Z

@@ Line 38: / Line 38: @@
 ==Operating System Oddities==
-While the purpose of the CROPS cli containers is to insulate the user from the vagaries of the host os, sometimes the oddness creeps in. Here's some of the host specific issues we've run into so far in case they affect you too.
+While the purpose of the CROPS cli containers is to insulate the user from the vagaries of the host os, sometimes the oddness creeps in. Instructions and explanations for Mac and Windows can be found here:
-=== Mac OSX ===
+https://github.com/crops/docker-win-mac-docs/wiki
 == Issues with File Paths ==

Bavery: /* eSDK */

2017-08-29T21:00:27Z

eSDK

← Older revision		Revision as of 21:00, 29 August 2017
Line 25:		Line 25:

	=== eSDK ===		=== eSDK ===
	The eSDK container is also generic in that it takes an extensible sdk install script as an argument so it can be used with a fairly arbitrary ext-sdk.		The eSDK container is also generic in that it takes an extensible sdk install script as an argument so it can be used with a fairly arbitrary ext-sdk. It works equally well with an old fashioned sdk (e.g. one without devtool but with a sysroot and a toolchain).

	=== Toaster ===		=== Toaster ===
	Toaster is more complicated. To facilitate quick startup, the Toaster containers include a database prepopulated from the layer index https://layers.openembedded.org. Because of this, the toaster containers come in a couple of varieties.		Toaster is more complicated. To facilitate quick startup, the Toaster containers include a database prepopulated from the layer index https://layers.openembedded.org. Because of this, the toaster containers come in a couple of varieties.

Bavery at 20:59, 29 August 2017

2017-08-29T20:59:34Z

← Older revision		Revision as of 20:59, 29 August 2017
Line 6:		Line 6:
	You may wonder why you would use these containers on Linux. The main reason is it gives you a guaranteed clean environment from which to build. Also it means you don't need to install the dependent packages required by the build tools. Measurements show '''no''' speed degradation when running in the container. This wiki assumes you have followed the basic documentation on the CROPS github Readme's (like https://github.com/crops/poky-container) and are looking for more tips.		You may wonder why you would use these containers on Linux. The main reason is it gives you a guaranteed clean environment from which to build. Also it means you don't need to install the dependent packages required by the build tools. Measurements show '''no''' speed degradation when running in the container. This wiki assumes you have followed the basic documentation on the CROPS github Readme's (like https://github.com/crops/poky-container) and are looking for more tips.

	~~== How to Get Started ==~~
	The setup on Mac and Windows requires some extra steps before you get up and running. This is due to the fact that neither the Mac nor the Windows file systems support all the features we need to do a build. To deal with this issue on these OS's we put the build into a persistent docker volume (https://docs.docker.com/engine/tutorials/dockervolumes/) and expose it to the host OS using a Samba container. The detailed instructions for doing this are located at https://github.com/crops/docker-win-mac-docs/wiki

	If you plan to use these containers on Linux, you can skip the docker volume and the Samba container instructions as they are unnecessary. The detailed instructions for running the various containers are located in the README.md for each container source on github. Pointers to these instructions for the Poky,eSDK, and Toaster containers are located at the bottom of the above referenced wiki.
	<br>		<br>
	<strong> NOTE: ALL the CROPS containers take a --help argument in case you forget the options! For example:</strong>		<strong> NOTE: ALL the CROPS containers take a --help argument in case you forget the options! For example:</strong>

Bavery: /* Introduction */

2017-08-29T20:58:51Z

Introduction

← Older revision		Revision as of 20:58, 29 August 2017
Line 4:		Line 4:
	The containers themselves are available on Dockerhub at https://hub.docker.com/u/crops/dashboard/		The containers themselves are available on Dockerhub at https://hub.docker.com/u/crops/dashboard/

	You may wonder why you would use these containers on Linux. The main reason is it gives you a guaranteed clean environment from which to build. Also it means you don't need to install the dependent packages required by the build tools. Measurements show '''no''' speed degradation when running in the container.		You may wonder why you would use these containers on Linux. The main reason is it gives you a guaranteed clean environment from which to build. Also it means you don't need to install the dependent packages required by the build tools. Measurements show '''no''' speed degradation when running in the container. This wiki assumes you have followed the basic documentation on the CROPS github Readme's (like https://github.com/crops/poky-container) and are looking for more tips.

	== How to Get Started ==		== How to Get Started ==

Bavery: /* Issues with File Paths */

2017-08-29T20:57:18Z

Issues with File Paths

← Older revision		Revision as of 20:57, 29 August 2017
Line 70:		Line 70:
	docker run --rm -it -v $(pwd):$(pwd) crops/poky --workdir=$(pwd)		docker run --rm -it -v $(pwd):$(pwd) crops/poky --workdir=$(pwd)
	This way, inside the container you have the same directory path as you do outside of the container. For things like		This way, inside the container you have the same directory path as you do outside of the container. For things like
	devtool modify ~~busyboxl~~		devtool modify busybox
	devtool find-recipe busybox		devtool find-recipe busybox
	this can make cutting and pasting easier from the "in container terminal" which lacks an editor into the editor or terminal with an editor on the host system.		this can make cutting and pasting easier from the "in container terminal" which lacks an editor into the editor or terminal with an editor on the host system.

Bavery at 17:28, 29 August 2017

2017-08-29T17:28:21Z

← Older revision		Revision as of 17:28, 29 August 2017
Line 62:		Line 62:
	=== Windows ===		=== Windows ===
	The biggest issue for Windows so far is that Windows 10 Pro, Enterprise, and Education can use [https://docs.docker.com/docker-for-windows/ Docker for Windows ] while earlier versions of Windows need to use [https://docs.docker.com/toolbox/overview/ Docker Toolbox]. Docker for Windows matches what is used on the Mac and is very similar to the experience on Linux. Docker Toolbox insets a VM (by default Virtualbox) in between the host and the cotainers.		The biggest issue for Windows so far is that Windows 10 Pro, Enterprise, and Education can use [https://docs.docker.com/docker-for-windows/ Docker for Windows ] while earlier versions of Windows need to use [https://docs.docker.com/toolbox/overview/ Docker Toolbox]. Docker for Windows matches what is used on the Mac and is very similar to the experience on Linux. Docker Toolbox insets a VM (by default Virtualbox) in between the host and the cotainers.

			== Issues with File Paths ==
			While the default way to run the containers (using crops/poky as an example but this applies equally well to the others).
			docker run --rm -it -v /home/myuser/mystuff:/workdir crops/poky --workdir=/workdir
			highlights the fact that the directory path inside the container is <strong>independent</strong> of the directory path on the host, this can sometimes be confusing. So, it is also quite reasonable to run the container like so:
			cd /home/myuser/mystuff
			docker run --rm -it -v $(pwd):$(pwd) crops/poky --workdir=$(pwd)
			This way, inside the container you have the same directory path as you do outside of the container. For things like
			devtool modify busyboxl
			devtool find-recipe busybox
			this can make cutting and pasting easier from the "in container terminal" which lacks an editor into the editor or terminal with an editor on the host system.

Bavery: /* Poky */

2017-08-29T17:14:34Z

Poky

← Older revision		Revision as of 17:14, 29 August 2017
Line 26:		Line 26:
	== Variations Explained ==		== Variations Explained ==
	=== Poky ===		=== Poky ===
	The default Poky container is quite generic and will work with most recent releases of YP. Despite the name, it simply contains all the dependent packages required by Poky but not the meta-data. It will work equally well for an OE Core setup. The default container is based on Ubuntu~~-14~~.~~04.~~ We are in the process of creating ones based on the rest of the standard supported Linux Distro's. For the common usage; however, which Distro is inside is irrelevant since everything is already set up for the user.		The default Poky container is quite generic and will work with most recent releases of YP. Despite the name, it simply contains all the dependent packages required by Poky but not the meta-data. It will work equally well for an OE Core setup. The default container is based on the latest Ubuntu LTS that YP supports. We are in the process of creating ones based on the rest of the standard supported Linux Distro's. For the common usage; however, which Distro is inside is irrelevant since everything is already set up for the user.

	=== eSDK ===		=== eSDK ===

Bavery: /* Windows */

2016-11-07T19:30:58Z

Windows

← Older revision		Revision as of 19:30, 7 November 2016
Line 61:		Line 61:
	Then you can rm the file. Alternatively, you could do the rm from with in a container and the linux side is less persnickety.		Then you can rm the file. Alternatively, you could do the rm from with in a container and the linux side is less persnickety.
	=== Windows ===		=== Windows ===
	The biggest issue for Windows so far is that Windows 10 Pro, Enterprise, and Education can use [https://docs.docker.com/docker-for-windows/ Docker for Windows ] while earlier versions of Windows need to use [ https://docs.docker.com/toolbox/overview/ Docker Toolbox]. Docker for Windows matches what is used on the Mac and is very similar to the experience on Linux. Docker Toolbox insets a VM (by default Virtualbox) in between the host and the cotainers.		The biggest issue for Windows so far is that Windows 10 Pro, Enterprise, and Education can use [https://docs.docker.com/docker-for-windows/ Docker for Windows ] while earlier versions of Windows need to use [https://docs.docker.com/toolbox/overview/ Docker Toolbox]. Docker for Windows matches what is used on the Mac and is very similar to the experience on Linux. Docker Toolbox insets a VM (by default Virtualbox) in between the host and the cotainers.