RISC-V is the only main architecture I see missing in the project. I am already using https://hub.docker.com/r/sorear/fedora-riscv-wip/ but it would be better to have the nice scrips from dockcross.

Document steps. Partial list:

• Create new directory and populate Dockerfile and Toolchain.cmake
  • When and how to use Debian / embedian / manylinux / centos / crosstool-ng
• Add to the Makefile for build and test targets for the image
• Add to .circleci/config.yml
• Add to README.md
• Push to DockerHub
• Add to MicroBadger

Per https://circleci.com/blog/circleci-hacks-reuse-yaml-in-your-circleci-config-with-yaml/

Since it may not be common knowledge, we should add an explicit, small, self-contained example of building against a dependency.

Two strategies can be demonstrated -- if it is a CMake project, we can show how to build against the dependency build tree by passing <depname>_DIR. We can also show how to install into a common local install prefix directory, then use it with CMake.

We should use a relatively small, simple dependency for the example.

Suggested-by: @fbudin69500

Similar to other arch's, CPP=aarch64-linux-gnu-cpp, but the file is aarch64-linux-gnu-cpp-4.9

I am trying to run armv6 cross compiler on docker for windows.

bahri@BGASUS MINGW64 /c/workspace/test-pi-cross
$ docker run --rm dockcross/linux-armv6 > ./dockcross

bahri@BGASUS MINGW64 /c/workspace/test-pi-cross
$ ./dockcross bash
[root:/work] # ls
CMakeLists.txt HelloWorld.cpp build-lin-x64 dockcross helloworld.c
[root:/work] # echo "int main(){return 0;}" > test.c
[root:/work] # cat test.c
int main(){return 0;}
[root:/work] # $CC test.c
cc1: fatal error: test.c: Value too large for defined data type
compilation terminated.
[root:/work] 1 # cp test.c /tmp/
[root:/work] # $CC /tmp/test.c
[root:/work] # exit
exit

I think this bug is related to docker/for-win#15, ie, the cross compiler executable itself is not build with large file offset support. Same problem does not occur with linux-x64 cross compiler image.

When I try to compile something use dockcross/linux-mipsel, I got an error:

make: /usr/bin/mips-linux-gnueabi-gcc: Command not found

I found lots of file named mipsel-linux-gnu-* in /usr/bin. Then I modified envirment and the error is gone.

export CROSS_TRIPLE=mipsel-linux-gnu
export AS=/usr/bin/mipsel-linux-gnu-as
export AR=/usr/bin/mipsel-linux-gnu-ar
export CC=/usr/bin/mipsel-linux-gnu-gcc
export CPP=/usr/bin/mipsel-linux-gnu-cpp-4.9
export CXX=/usr/bin/mipsel-linux-gnu-g++
export LD=/usr/bin/mipsel-linux-gnu-ld

I think the value of CROSS_TRIPLE should be "mipsel-linux-gnu" in Dockerfile.

I'm trying to use dockcross to provide a pre-setup environment for building yocto.

I am currently using the dockcross-linux-x64 image and installing the following additional dependencies.

gosu root apt-get install gawk diffstat unzip texinfo chrpath socat cpio gcc-multilib

Technically since Yocto builds the toolchain, I don't need the cross compile setup provided in the linux-x64 image.

However I'm not sure how best to add this ability to dockcross. These packages could be added to common.debian. Or a dockcross-yocto image could be created.

Any input would be appreciated.

The image on the hub is 16 hours old, but does not contain the conan part? Is this by design or an error ?

Hi, I ran dockcross-linux-armv7 bash and want to get a root privilege to install packages (via apt-get), however sudo command not found, and I don't know password of root user so cannot su root. Any chance to add sudo or any related utils in order to gain root access?

Hi there, I'am using dockcross in jenkins docker container

I built my jenkins docker image for android support, just call it ci_service

I ran jenkins docker with this:

docker run -d -p 8080:8080 -p 50000:50000 \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /home/dev/jenkins:/var/jenkins_home \
-v /opt/jenkins-extra/android-sdk:/opt/android-sdk \
-v /opt/jenkins-extra/bin:/opt/docker-cross \
-v /opt/jenkins-extra/gradle-3.4.1:/opt/gradle \
--name=ci_service ci_service:0.1

After running jenkins in detached mode, I executed

docker exec -u root -it ci_service bash

and obtained a cli session, then I went to the jenkins project directory, executed dockcross scripts, but got errors:

root@048fb1b14d84:/var/jenkins_home/workspace/c_test# ls
LICENSE  README.md  hello.c

root@048fb1b14d84:/var/jenkins_home/workspace/c_test# /opt/docker-cross/linux-armv7 bash -c '$CC hello.c -o hello_arm'
cp: target '/home/root/' is not a directory
chown: cannot access '/home/root/*': No such file or directory
arm-linux-gnueabihf-gcc: error: main.c: No such file or directory
arm-linux-gnueabihf-gcc: fatal error: no input files
compilation terminated.

and when I ran it as user jenkins, I got this:

jenkins@048fb1b14d84:~/workspace/c_test$ /opt/docker-cross/linux-armv7 bash -c '$CC hello.c -o hello_arm'
arm-linux-gnueabihf-gcc: error: hello.c: No such file or directory
arm-linux-gnueabihf-gcc: fatal error: no input files
compilation terminated.

It seems current directory was not copied to container.

But it works great in native host.

are there anything wrong with my operation? I am pretty new to dockcross, thanks a lot

For example, the following fails:

$ docker pull dockcross/manylinux-x64 
$ docker run --rm dockcross/manylinux-x64 > ~/bin/dockcross-manylinux-x64
$ chmod u+x ~/bin/dockcross-manylinux-x64
$ dockcross-manylinux-x64 update-image
chpst: fatal: unable to run: update-image: file does not exist

Since internally scikit-build runs command like cmake --build <dir> ..., systematically passing -DCMAKE_TOOLCHAIN_FILE:FILEPATH=... is problematic.

Path forward:

Few options:

1. Find a way to exclude the following from common.docker:

COPY imagefiles/cmake.sh /usr/local/bin/cmake
COPY imagefiles/ccmake.sh /usr/local/bin/ccmake

1. We could update imagefiles/cmake.sh and imagefiles/ccmake.sh so that these scripts conditionally pass -DCMAKE_TOOLCHAIN_FILE.

   a. Invoke with -DCMAKE_TOOLCHAIN_FILE only if environment variable DOCKCROSS_CMAKE_WITH_TOOLCHAIN is set to 1, all docker images would have this environment variable set expect the manylinux one.

   b. Or the other way around, the environment variable could be DOCKCROSS_CMAKE_WITHOUT_TOOLCHAIN and build a wheel would have to be done calling DOCKCROSS_CMAKE_WITHOUT_TOOLCHAIN=1 /opt/python/cp27-cp27m/bin/python setup.py bdist_wheel

I will most likely go with option 2a

It looks like "linux-mipsel" is missing from the .circleci-matrix.yml file, causing the dockcross/linux-mipsel image to be stale.

I noticed that CROSS_TRIPLE should be using "mipsel-linux-gnu", but the current dockcross/linux-mipsel image is stale and uses mips-linux-gnu, which is invalid. It looks like this was fixed
upstream.

Reproduction:

$ docker pull dockcross/linux-mips
$ docker run -ti dockcross/linux-mipsel bash
$ echo $CROSS_TRIPLE
mips-linux-gnueabi
$ echo $CC
/usr/bin/mips-linux-gnueabi-gcc

        "RepoTags": [
            "dockcross/linux-mipsel:latest"
        ],
        "RepoDigests": [
            "dockcross/linux-mipsel@sha256:27bee874a434a2f5ff8fda1d393076c47eac6cea8e4db8c686a119da2f4dc35f"
        ],
        "Parent": "",
        "Comment": "",
        "Created": "2017-01-22T23:45:36.797142644Z",
        "Container": "b276e0c4e9612551d195fb9e896d4551c98b522322e9c71b6dbad063c7610066",

Error deleting container: Error response from daemon: Driver btrfs failed to remove root filesystem 4f624cfcf5b2362e35b564958f257669bd631081e8bd74544aeea9a623f6684a: Failed to destroy btrfs snapshot /var/lib/docker/btrfs/subvolumes for 4f624cfcf5b2362e35b564958f257669bd631081e8bd74544aeea9a623f6684a: operation not permitted

As specified here, we could build the images specifying --rm=false. That said, then, we would have to probably explicitly delete the intermediate container.

An other related read is https://discuss.circleci.com/t/docker-error-removing-intermediate-container/70

and some relevant part of the discussion copied below:

User:

That would be great to get this issue fixed so that docker run --rm works. I use --rm to clean up
containers after they have been run locally on my development machine. It would be a shame to add
special code for tests to pass on CircleCI.

CircleCI support:

Not sure if this can be fixed since the problem appears to be related to docker
running in an unprivileged LXC container. CircleCI will likely never use privileged LXC containers for
builds. This would need to be fixed upstream on the Docker/LXC side.

Resources:

• https://docs.docker.com/engine/reference/commandline/build/

This looks similar to #123. The latest build of "linux-armv7" seems to have the incorrect CPP environment variable:

$ echo $CPP
/usr/bin/arm-linux-gnueabihf-cpp
$ ls -la $CPP*
-rwxr-xr-x 1 root root 801656 Mar 14  2015 /usr/bin/arm-linux-gnueabihf-cpp-4.9

Container linux-armv7:latest:

        "Id": "sha256:731002bfb477f8627b783d9f4f4bdda9a487280b093682be560c58cc0c6ac1be",

For CPython 2.7 and 3.4 build support

http://mingwpy.github.io/

Hi :
My test OS is ubuntu 15.04 on a X64 machine

I used ./dokcross-win-86 bash -c '$CC hello.c -o hello' to test the usage,
it worked great.

But when I use the ./dokcross-win-86 in a project containing a make file , it failed
I used it like ::
./dokcross-win-86 make
And then I filed the output file, it returned ::
ELF 64-bit LSB executable, x86-64, version 1 (SYSV)......

the cross compile failed, then I thought maybe I could force the make command run in the container
So i tried ::
./dokcross-win-86 -- make
it still didn't work

Did I miss anything?

Thanks for your help

Hi guys,

Hope you are all well !

I was wondering if some docker base images could be shrinked in size by using an Alpine for the base.

Have a great day !

Cheers,
Richard

Hi,

I am trying to compile SimpleITK using dockercross. When the SuperBuild tries to git clone ITK, I get the following error:

[ 17%] Performing download step (git clone) for 'ITK'
Cloning into 'ITK'...
error: SSL: certificate subject name '*.kitware.com' does not match target host name 'itk.org' while accessing http://itk.org/ITK.git/info/refs?service=git-upload-pack

What am I missing?

Thanks for maintaining this great project, it sure saves a lot of hassle in managing toolchains!

Apologies for the n00bish question, but I was wondering how would I go about including python-dev, for example. I need that to compile some swig related C library, which is searching for Python.h header file:#include <Python.h>.

I am thinking that simply modifying the Dockerfile to include the needed package would do the trick, but was wondering if this project comes with more elegant solutions.

dockcross/linux-x86 has no sudo installed, as a result it is not possible to install new packages

 docker run --rm dockcross/linux-x86 > ./dockcross
./dockcross bash -c 'sudo -i'
bash: sudo: command not found

Integrates this patch:

https://gitlab.kitware.com/cmake/cmake/merge_requests/217

Following the instructions in the readme generates an error on MacOS.

docker run --rm dockcross/linux-armv7 > ./dockcross-linux-armv7
chmod +x ./dockcross-linux-armv7
./dockcross-linux-armv7 bash -c '$CC test/C/hello.c -o hello_arm'
grep: /proc/version: No such file or directory
grep: /proc/version: No such file or directory

There is no /proc filesystem on MacOS.
This does not appear to be a fatal error, and the executable is still produced.

dockcross update-script creates docker containers, but does not remove them.

$ docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS                   PORTS               NAMES
$ ./dockcross-linux-x64 update-script
./dockcross-linux-x64 is up to date
$ docker ps -a
CONTAINER ID        IMAGE                 COMMAND                  CREATED             STATUS                     PORTS               NAMES
a2cd23e296cd        dockcross/linux-x64   "/dockcross/entrypoin"   4 seconds ago       Exited (0) 3 seconds ago                       happy_goldstine

Are there plans to support MacOS as well?

I saw this project https://github.com/tpoechtrager/osxcross, could that be delivered as a docker image?

All dockcross containers provide a CMake toolchain file in the CMAKE_TOOLCHAIN_FILE environmental variable. Ensure that this is always passed to CMake.

What's the docker trying to do when permission is denied? Note that this directory is NFS mounted but I can manually create directories. Let me know if there is some debugging I can do.

 $ dockcross-linux-armv5 gcc -v
docker: Error response from daemon: mkdir /home/jcormier/projects/l138/mtd-utils: permission denied.
 $ mkdir test
 $ echo $?
0
 $ pwd
/home/jcormier/projects/l138/mtd-utils/tests/fs-tests/integrity

It would be nice to set the ARCH environment variable in each image. It looks redundant to set while running the container, i.e. docker run ... -e ARCH=arm dockercross/linux-armv7

Rational: check for issue like the one reported in #94

Considering CircleCi can not be used to run images on both Linux and OSX at the same time, a solution could be to use travis-ci.

Test on travis would have to be triggered only if the dockcross tests are successful.

This could be done by creating a dummy branch named successful-build-log, after successful execution of all dockcross tests and upload of images on dockerhub, a commit would be added to this branch ... this commit would trigger build on travis-ci.

Is it possible to have conan.io added to the image ?

For easily building Python C extensions with CMake for PyPI.

I successfully compiled haproxy for mipsel(little endine), but my device is mips(big endian). Is there some way use dockcross/linux-mipsel to compile for mips? Maybe set some switch?

Linux dockcross images current operate by:

1. Installing a base debian:jessie-based image.
2. Installing a crossbuild-essential- toolchain variant.
3. Hook that variant up to the environment.

This works so long as a crossbuild-* variant is available for the intended platform. It also is worth noting that crossbuild-* packages seem to have been deprecated after Jessie, and the new roadmap doesn't seem really known or straightforward.

While trying to build a big-endian MIPS compiler, I encountered a problem where Jessie didn't have a prebuilt package for that architecture. The solution that I settled on uses crosstool-ng, a really cool versatile toolchain builder project.

I created a branch to try and solve two problems at once: remove dependency on Debian's hairy cross-compiler story, and enable support for a much wider variety of configurations. The approach that I took can be seen here: https://github.com/danjacques/dockcross/tree/linux-mips (compare).

Notably, this add support for an alternative toolchain construction using crosstool-ng. A target that uses this approach defines a Makefile and Toolchain.cmake, similar to current Linux targets, as well as a new crosstool-ng config which specializes the cross-compiler suite that gets installed.

I'm interested in opinions on this approach, or other ideas for how to add support for a more general set of platforms to dockcross (if this is actually something the project wants to do).

I want to use dockcross/browser-asmjs to build c code to js,
error occured while linking
All DICompileUnits must be listed in llvm.dbg.cu
/emsdk_portable/clang/tag-e1.37.3/build_tag-e1.37.3_64/bin/opt: CMakeFiles/fjwDecodec_lib.dir/fjwDecodec/HEVC_DCT_QUANTIZATION/dct_zigzag.c.o: error: input module is broken!
Traceback (most recent call last):
File "/emsdk_portable/emscripten/tag-1.37.3/emcc", line 13, in
emcc.run()
File "/emsdk_portable/emscripten/tag-1.37.3/emcc.py", line 1631, in run
final = shared.Building.llvm_opt(final, link_opts, DEFAULT_FINAL)
File "/emsdk_portable/emscripten/tag-1.37.3/tools/shared.py", line 1751, in llvm_opt
assert os.path.exists(target), 'Failed to run llvm optimizations: ' + output
AssertionError: Failed to run llvm optimizations:
CMakeFiles/fjwDecodec_lib.dir/build.make:4984: recipe for target 'fjwDecodec_lib.js' failed
make[2]: *** [fjwDecodec_lib.js] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/fjwDecodec_lib.dir/all' failed
make[1]: *** [CMakeFiles/fjwDecodec_lib.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

and i donot know how to do

I would like to compile Radare2 project https://radare.org/r/ through dockcross/linux-mipsel but I have got problem with missing "/usr/bin/mips-linux-gnueabi-gcc".

Below my compile log:

$ git clone https://github.com/radare/radare2.git
$ docker run --rm dockcross/linux-mipsel > ./dockcross
$ chmod +x dockcross
...
$ ./dockcross ./sys/install.sh

WARNING: Updating from remote repository
Already up-to-date.
sudo: not found

export USE_R2_CAPSTONE

configure-plugins: Loading ./plugins.def.cfg ..
configure-plugins: Generating libr/config.h ..
configure-plugins: Generating libr/config.mk ..
SHARED: io.shm
STATIC: anal.6502 anal.8051 anal.arc anal.arm_cs anal.arm_gnu anal.avr anal.bf anal.cr16 anal.cris anal.dalvik anal.ebc anal.gb anal.h8300 anal.i4004 anal.i8080 anal.java anal.m68k_cs anal.malbolge anal.mips_cs anal.mips_gnu anal.msp430 anal.nios2 anal.null anal.pic18c anal.ppc_cs anal.ppc_gnu anal.riscv anal.rsp anal.sh anal.snes anal.sparc_cs anal.sparc_gnu anal.sysz anal.tms320 anal.v810 anal.v850 anal.vax anal.ws anal.x86_cs anal.x86_udis anal.xap anal.xcore_cs anal.xtensa anal.z80 asm.6502 asm.8051 asm.arc asm.arm_as asm.arm_cs asm.arm_gnu asm.arm_winedbg asm.avr asm.bf asm.cr16 asm.cris_gnu asm.dalvik asm.dcpu16 asm.ebc asm.gb asm.h8300 asm.hppa_gnu asm.i4004 asm.i8080 asm.java asm.lanai_gnu asm.lh5801 asm.lm32 asm.m68k_cs asm.malbolge asm.mcs96 asm.mips_cs asm.mips_gnu asm.msp430 asm.nios2 asm.pic18c asm.ppc_cs asm.ppc_gnu asm.rar asm.riscv asm.rsp asm.sh asm.snes asm.sparc_cs asm.sparc_gnu asm.spc700 asm.sysz asm.tms320 asm.tricore asm.v810 asm.v850 asm.vax asm.wasm asm.ws asm.x86_as asm.x86_cs asm.x86_nasm asm.x86_nz asm.x86_udis asm.xap asm.xcore_cs asm.xtensa asm.z80 bin.any bin.art bin.avr bin.bf bin.bflt bin.bios bin.bootimg bin.cgc bin.coff bin.dex bin.dol bin.dyldcache bin.elf bin.elf64 bin.fs bin.java bin.mach0 bin.mach064 bin.mbn bin.menuet bin.mz bin.nes bin.nin3ds bin.ninds bin.ningb bin.ningba bin.nro bin.omf bin.p9 bin.pe bin.pe64 bin.pebble bin.psxexe bin.rar bin.smd bin.sms bin.spc700 bin.te bin.vsf bin.wasm bin.xbe bin.zimg bin_xtr.fatmach0 bin_xtr.xtr_dyldcache bp.arm bp.bf bp.mips bp.ppc bp.x86 core.anal core.java crypto.aes crypto.aes_cbc crypto.base64 crypto.base91 crypto.blowfish crypto.cps2 crypto.des crypto.punycode crypto.rc2 crypto.rc4 crypto.rc6 crypto.rol crypto.ror crypto.rot crypto.xor debug.bf debug.bochs debug.esil debug.gdb debug.io debug.native debug.qnx debug.rap debug.wind egg.exec egg.xor fs.cpio fs.ext2 fs.fat fs.fb fs.hfs fs.hfsplus fs.iso9660 fs.jfs fs.minix fs.ntfs fs.posix fs.reiserfs fs.sfs fs.squash fs.tar fs.udf fs.ufs fs.xfs io.bfdbg io.bochs io.debug io.default io.gdb io.gzip io.http io.ihex io.mach io.malloc io.mmap io.procpid io.ptrace io.qnx io.r2k io.r2pipe io.r2web io.rap io.self io.shm io.sparse io.tcp io.w32 io.w32dbg io.windbg io.zip lang.vala parse.6502_pseudo parse.arm_pseudo parse.att2intel parse.dalvik_pseudo parse.m68k_pseudo parse.mips_pseudo parse.mreplace parse.ppc_pseudo parse.x86_pseudo
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for working directories... current
using prefix '/usr'
checking for c compiler... no
cleaning temporally files... done
ERROR: /usr/bin/mips-linux-gnueabi-gcc cannot create executables

$ ./dockcross bash -c '$CC ./configure'
bash: /usr/bin/mips-linux-gnueabi-gcc: No such file or directory

Tested on:

Linux 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

and

Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux

Maybe I do it somethin wrong.

Thank you

Note the manylinux-x64 used here include patch associated with #38

Here is the error I get when trying to build the wheel for CMake:

$ git clone [email protected]:jcfr/cmake-python-distributions.git
$ cd cmake-python-distributions
$ dockcross-manylinux-x64 /opt/python/cp27-cp27m/bin/python setup.py build
[...]
-- verifying file...
       file='/work/_skbuild/cmake-build/CMakeProject-src-download-prefix/src/cmake-3.6.2.tar.gz'
-- SHA256 hash of
    /work/_skbuild/cmake-build/CMakeProject-src-download-prefix/src/cmake-3.6.2.tar.gz
  does not match expected value
    expected: '189ae32a6ac398bb2f523ae77f70d463a6549926cde1544cd9cc7c6609f8b346'
      actual: 'e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855'
-- File already exists but hash mismatch. Removing...
-- downloading...
       src='https://cmake.org/files/v3.6/cmake-3.6.2.tar.gz'
       dst='/work/_skbuild/cmake-build/CMakeProject-src-download-prefix/src/cmake-3.6.2.tar.gz'
       timeout='none'
error: downloading 'https://cmake.org/files/v3.6/cmake-3.6.2.tar.gz' failed
  status_code: 1
  status_string: "Unsupported protocol"
  log:

Using dockcross/linux-armv6 works great expect for the special case where the device has no hard-float because the linking is done against:

/lib/ld-linux-armhf.so.3 .

I have this special case that one of my device does not support hard-float and has only /lib/ld-linux.so.3 .

Trying to use arm-linux-gnueabi-gcc fails because it is not present in the image.

I would be nice if both (soft-float and hard-float) would be supported.

Hi,

Thanks for these awesome docker images.

Is it possible to add bare metal cross compiler support?

missing /usr/bin/arm-linux-gnueabi-cpp , only /usr/bin/arm-linux-gnueabi-cpp-4.9

This should hopefully address timeout issues in #155 by allowing configuration of resource_class of the and better parallelism via Workflows.

When the version of pip provided by the image is not the latest, running command the one reported below fails.

Few approaches:

• Allow manylinux images to update imagefiles/entrypoint.sh to check for a pre_chown_hook to give an opportunity for the script to change the ownership of the site-packages folder associated with the different python installs.
• hack imagefiles/entrypoint.sh and hardcode the expected behavior

[scikit-ci] Executing: ./dockcross /opt/python/cp27-cp27mu/bin/python -m pip install --disable-pip-version-check --upgrade pip
Collecting pip
  Downloading pip-9.0.0-py2.py3-none-any.whl (1.3MB)
Installing collected packages: pip
  Found existing installation: pip 8.1.2
    Uninstalling pip-8.1.2:
Exception:
Traceback (most recent call last):
  File "/opt/python/cp27-cp27mu/lib/python2.7/site-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
  File "/opt/python/cp27-cp27mu/lib/python2.7/site-packages/pip/commands/install.py", line 317, in run
    prefix=options.prefix_path,
  File "/opt/python/cp27-cp27mu/lib/python2.7/site-packages/pip/req/req_set.py", line 736, in install
    requirement.uninstall(auto_confirm=True)
  File "/opt/python/cp27-cp27mu/lib/python2.7/site-packages/pip/req/req_install.py", line 742, in uninstall
    paths_to_remove.remove(auto_confirm)
  File "/opt/python/cp27-cp27mu/lib/python2.7/site-packages/pip/req/req_uninstall.py", line 115, in remove
    renames(path, new_path)
  File "/opt/python/cp27-cp27mu/lib/python2.7/site-packages/pip/utils/__init__.py", line 267, in renames
    shutil.move(old, new)
  File "/opt/python/cp27-cp27mu/lib/python2.7/shutil.py", line 303, in move
    os.unlink(src)
OSError: [Errno 13] Permission denied: '/opt/_internal/cpython-2.7.11-ucs4/bin/pip'

Just a question or maybe an enhancement request.
Is there any plan for updating the dockcross images to be based on stretch instead of jessie?
How would that look? A separate branch? fork? or just advance master?
BTW - I think these images are great.

Described here:

https://microbadger.com/?utm_source=ilbrokentag&utm_medium=email&utm_campaign=microbadgeril#/labels

To reproduce:

1. create a file named test-download.cmake with the following content:

message(STATUS "Downloading ... ")
file(
  DOWNLOAD 
   "https://cmake.org/files/v3.6/cmake-3.6.2.tar.gz"
   "/work/cmake-3.6.2.tar.gz"
  STATUS status
  SHOW_PROGRESS
  )

message("status:${status}")

2. Execute:

± cmake -P test-download.cmake 
-- Downloading ... 
status:1;"Unsupported protocol"

Version of cmake is:

± cmake --version
cmake version 3.7.20161102-gab2ae4

thanks

When building the base image, the following error is printed. Notes:

• it doesn't prevent the build from completing.
• it doesn't happen for the manylinux images

Code causing triggering the error is in common.docker:

  WRAPPER=$( [ "$DEFAULT_DOCKCROSS_IMAGE" = "dockcross/manylinux-x86" ] && echo "linux32" || echo "") && \
  CONFIG_FLAG=$( [ "$DEFAULT_DOCKCROSS_IMAGE" = "dockcross/manylinux-x86" ] && echo "-m32" || echo "") && \

Running on latest of anything is almost never preferable, instead one should keep versioning completely under control to avoid "it worked before"-kind of issues.

So, as title says:
Please add tags to the images (preferably the git-repo too).

Anyways, great work with it all! :) 💯👍