IoTGateway/Docker - Revision history

Jems.cheng at 02:38, 2 May 2024

2024-05-02T02:38:16Z

Jems.cheng at 06:27, 10 April 2023

2023-04-10T06:27:42Z

Clayder.huang at 08:49, 6 May 2022

2022-05-06T08:49:07Z

Phill.liu at 00:44, 8 June 2021

2021-06-08T00:44:59Z

Phill.liu at 00:43, 8 June 2021

2021-06-08T00:43:39Z

Phill.liu at 09:54, 19 March 2021

2021-03-19T09:54:13Z

Phill.liu at 09:53, 19 March 2021

2021-03-19T09:53:49Z

Phill.liu at 09:42, 19 March 2021

2021-03-19T09:42:40Z

Phill.liu at 09:29, 19 March 2021

2021-03-19T09:29:15Z

Phill.liu at 09:28, 19 March 2021

2021-03-19T09:28:55Z

@@ Line 261: / Line 261: @@
   curl [https://raw.githubusercontent.com/rockchip-linux/repo/stable/repo https://raw.githubusercontent.com/rockchip-linux/repo/stable/repo] > ${HOME}/bin/repo
 == References ==
-<references />
+&nbsp;
 *External Link
 #[https://philipzheng.gitbooks.io/docker_practice/content/index.html Docker Introduction (Chinese)]
 [[Category:Technique]]

@@ Line 1: / Line 1: @@
 Use Docker to set up build environment more safely & quickly
@@ Line 21: / Line 22: @@
 === Get base image ===
-To get the images we provided, you can use ''docker pull &lt;IMAGE REPOSITORY&gt;'' to get the images in the ''[[#Image_List|image list]]''.
+To get the images we provided, you can use ''docker pull <IMAGE REPOSITORY>'' to get the images in the ''[[#Image_List|image list]]''.
   $ docker pull advrisc/u12.04-imx6lbv3:20160303
@@ Line 75: / Line 76: @@
 e9548a0d40     advrisc/u12.04-imx6lbv3:20160303   "/bin/bash"    27 seconds ago     Exited (0) 4 seconds ago              dreamy_jennings
-To enter the container that you've created, you need to do ''docker start &lt;CONTAINER ID&gt;'' & ''docker attach &lt;CONTAINER ID&gt;''.
+To enter the container that you've created, you need to do ''docker start <CONTAINER ID>'' & ''docker attach <CONTAINER ID>''.
   $ docker start 89e9548a0d40
@@ Line 87: / Line 88: @@
 There are two ways to share data with host OS.
 *data volume
 *docker cp
 You have to assign data volumes when creating the container. Use ''docker run'' with '''-v''' options to enable data volume. In the case below, we mount the BSP directory (/home/root/imx6LBV5080_2016-02-03) from your Docker daemon’s host into a container. So, you can access the source code at /home/adv/BSP in the container.
@@ Line 97: / Line 98: @@
   adv@7bc2d878c870:~$ sudo chown adv:adv -R BSP
-Alternatively, you can also access data in containers after the container is created. Use ''docker cp &lt;CONTAINER:PATH&gt; &lt;LOCALPATH&gt;'' to pull out data from the container, or ''docker cp &lt;LOCALPATH&gt; &lt;CONTAINER:PATH&gt;'' to push data into the container.
+Alternatively, you can also access data in containers after the container is created. Use ''docker cp <CONTAINER:PATH> <LOCALPATH>'' to pull out data from the container, or ''docker cp <LOCALPATH> <CONTAINER:PATH>'' to push data into the container.
   // Copy sdcard image from container to host
@@ Line 107: / Line 108: @@
 === Remove image or container ===
-Once you do not need the container, you can use ''docker rm &lt;CONTAINER ID&gt;'' to remove it.
+Once you do not need the container, you can use ''docker rm <CONTAINER ID>'' to remove it.
   $ docker rm 89e9548a0d40
 e9548a0d40
-If you want to remove Docker base image, use ''docker rmi &lt;IMAGE ID&gt;''
+If you want to remove Docker base image, use ''docker rmi <IMAGE ID>''
   $ docker rmi advrisc/u12.04-imx6lbv3:20160303
@@ Line 120: / Line 121: @@
 It's very easy to build our BSP in Docker environment.
 #Get BSP source code
 #Run a Docker container with data volume sharing for the BSP, or you can use ''docker cp'' to put BSP into the container.
 #In the container, go to BSP folder and follow the same introductions as you do on normal computer.
 #Finally, copy your images from container to host.
 == Image List ==
@@ Line 139: / Line 140: @@
 | 20170103
 | Ubuntu 12.04
-| Freescale i.MX6 Yocto 1.5 (fsl-yocto-3.10.17_1.0.x)<br/>Freescale i.MX6 Yocto 1.7 (fsl-yocto-3.14.28_1.0.0)<br/>Freescale i.MX6 Yocto 1.8 (fsl-yocto-3.14.52_1.1.0)<br/>Freescale i.MX6 Yocto 2.0 (fsl-yocto-4.1.15_1.1.0)<br/>Freescale i.MX6 Yocto 2.1 (fsl-yocto-4.1.15_2.0.0)
+| Freescale i.MX6 Yocto 1.5 (fsl-yocto-3.10.17_1.0.x)<br/> Freescale i.MX6 Yocto 1.7 (fsl-yocto-3.14.28_1.0.0)<br/> Freescale i.MX6 Yocto 1.8 (fsl-yocto-3.14.52_1.1.0)<br/> Freescale i.MX6 Yocto 2.0 (fsl-yocto-4.1.15_1.1.0)<br/> Freescale i.MX6 Yocto 2.1 (fsl-yocto-4.1.15_2.0.0)
 |-
 | [https://hub.docker.com/r/advrisc/u12.04-quarklbv2 advrisc/u12.04-quarklbv2]
 | 20160621
 | Ubuntu 12.04
-| Intel Quark Yocto 1.4.2 (Intel Quark BSP 1.0.4)<br/>Intel Quark Yocto 1.7.2 (Intel Quark BSP 1.2.0)
+| Intel Quark Yocto 1.4.2 (Intel Quark BSP 1.0.4)<br/> Intel Quark Yocto 1.7.2 (Intel Quark BSP 1.2.0)
 |-
 | [https://hub.docker.com/r/advrisc/u12.04-imx6abv1 advrisc/u12.04-imx6abv1]
@@ Line 154: / Line 155: @@
 | 20160809
 | Ubuntu 12.04
-| Freescale i.MX6 Android 4.3 (android_JB4.3_1.1.0)<br/>Freescale i.MX6 Android 4.4.2 (android_KK4.4.2_1.0.0)
+| Freescale i.MX6 Android 4.3 (android_JB4.3_1.1.0)<br/> Freescale i.MX6 Android 4.4.2 (android_KK4.4.2_1.0.0)
 |-
 | [https://hub.docker.com/r/advrisc/u14.04-imx6abv4 advrisc/u14.04-imx6abv4]
 | 20170310
 | Ubuntu 14.04
-| Freescale i.MX6 Android 5.0.0 (android_L5.0.0_1.0.0)<br/>Freescale i.MX6 Android 5.1.1 (android_L5.1.1_2.1.0)<br/>Freescale i.MX6 Android 6.0.1 (android_M6.0.1_1.0.0)
+| Freescale i.MX6 Android 5.0.0 (android_L5.0.0_1.0.0)<br/> Freescale i.MX6 Android 5.1.1 (android_L5.1.1_2.1.0)<br/> Freescale i.MX6 Android 6.0.1 (android_M6.0.1_1.0.0)
 |-
 | [https://hub.docker.com/r/advrisc/u16.04-imx6abv5 advrisc/u16.04-imx6abv5]
 | 20170523
 | Ubuntu 16.04
-| Freescale i.MX6 Android 7.0.0 (android_N7.1.1_1.0.0)<br/>Rockchip RK3399 Android 7.1.2
+| Freescale i.MX6 Android 7.0.0 (android_N7.1.1_1.0.0)<br/> Rockchip RK3399 Android 7.1.2
 |-
 | [https://hub.docker.com/r/advrisc/u14.04-410clbv1 advrisc/u14.04-410clbv1]
 | 20170717
 | Ubuntu 14.04
-| Qualcomm db410c Yocto 2.0 (oe-rpb-manifest ''jethro'')<br/>Qualcomm db410c Yocto 2.1 (oe-rpb-manifest ''krogoth'')<br/>Qualcomm db410c Yocto 2.2 (oe-rpb-manifest ''morty'')
+| Qualcomm db410c Yocto 2.0 (oe-rpb-manifest ''jethro'')<br/> Qualcomm db410c Yocto 2.1 (oe-rpb-manifest ''krogoth'')<br/> Qualcomm db410c Yocto 2.2 (oe-rpb-manifest ''morty'')
 |-
 | [https://hub.docker.com/r/advrisc/u14.04-am57lbv1/ advrisc/u14.04-am57lbv1]
@@ Line 200: / Line 201: @@
 == Bug Fix ==
 === Repo ===
@@ Line 221: / Line 221: @@
 make configure
 ./configure --prefix=/usr
-apt-get install asciidoc
+sudo apt-get install asciidoc
 make all doc
 sudo make install install-doc install-html
@@ Line 266: / Line 266: @@
 <references />
 *External Link
 [[Category:Technique]]

@@ Line 200: / Line 200: @@
 == Bug Fix ==
 === Repo ===
@@ Line 205: / Line 206: @@
 If your '''repo''' command is upgraded to&nbsp;v2.0 and above, you have to upgrade '''git''' & '''python3'''.
 *Git
 :Update to 2.10.2 or later.
   sudo apt-get update
@@ Line 227: / Line 228: @@
 </pre>
 :Update to 3.6 or later.
   sudo apt-get install -y python-software-properties
@@ Line 240: / Line 241: @@
   sudo add-apt-repository -y ppa:deadsnakes/ppa
   sudo apt-get update
   sudo apt-get install -y python3.6

@@ Line 214: / Line 214: @@
   wget [https://github.com/git/git/archive/v2.25.0.tar.gz https://github.com/git/git/archive/v2.32.0.tar.gz]
-  tar zxvf v2.25.0.tar.gz
+  tar zxvf v2.32.0.tar.gz
-  cd git-2.25.0/
+  cd git-2.32.0/
 <pre>sudo apt-get install autoconf
 sudo apt install git

@@ Line 209: / Line 209: @@
 :Update to 2.10.2 or later.
   sudo apt-get install -y libcurl4-openssl-dev
   sudo apt-get install -y tk gettext
-  wget [https://github.com/git/git/archive/v2.25.0.tar.gz https://github.com/git/git/archive/v2.25.0.tar.gz]
+  wget [https://github.com/git/git/archive/v2.25.0.tar.gz https://github.com/git/git/archive/v2.32.0.tar.gz]
   tar zxvf v2.25.0.tar.gz
   cd git-2.25.0/