Supported tags and respective
No supported tags found!
It is very likely that
gcc does not support the currently selected architecture (
Where to file issues:
the Docker Community
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What is GCC?
The GNU Compiler Collection (GCC) is a compiler system produced by the GNU Project that supports various programming languages. GCC is a key component of the GNU toolchain. The Free Software Foundation (FSF) distributes GCC under the GNU General Public License (GNU GPL). GCC has played an important role in the growth of free software, as both a tool and an example.
How to use this image
Start a GCC instance running your app
The most straightforward way to use this image is to use a gcc container as both the build and runtime environment. In your
Dockerfile, writing something along the lines of the following will compile and run your project:
FROM i386/gcc:4.9 COPY . /usr/src/myapp WORKDIR /usr/src/myapp RUN gcc -o myapp main.c CMD ["./myapp"]
Then, build and run the Docker image:
$ docker build -t my-gcc-app . $ docker run -it --rm --name my-running-app my-gcc-app
Compile your app inside the Docker container
There may be occasions where it is not appropriate to run your app inside a container. To compile, but not run your app inside the Docker instance, you can write something like:
$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp i386/gcc:4.9 gcc -o myapp myapp.c
This will add your current directory, as a volume, to the container, set the working directory to the volume, and run the command
gcc -o myapp myapp.c. This tells gcc to compile the code in
myapp.c and output the executable to myapp. Alternatively, if you have a
Makefile, you can instead run the
make command inside your container:
$ docker run --rm -v "$PWD":/usr/src/myapp -w /usr/src/myapp i386/gcc:4.9 make
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the
As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.