DEPRECATED

The aarch64 organization is deprecated in favor of the more-specific arm64v8 organization, as per https://github.com/docker-library/official-images#architectures-other-than-amd64⁠. Please adjust your usages accordingly.

Supported tags and respective Dockerfile links

** THESE IMAGES ARE VERY EXPERIMENTAL; THEY ARE PROVIDED ON A BEST-EFFORT BASIS WHILE docker-library/official-images#2289⁠ IS STILL IN-PROGRESS (which is the first step towards proper multiarch images) **

** PLEASE DO NOT USE THEM FOR IMPORTANT THINGS **

This image is built from the source of the official image of the same name (gcc). Please see that image's description for links to the relevant Dockerfiles.

If you are curious about specifically how this image differs, see the Jenkins Groovy DSL scripts in the tianon/jenkins-groovy GitHub repository⁠, which are responsible for creating the Jenkins jobs which build them.

Quick reference

• Where to get help:
  the Docker Community Forums⁠, the Docker Community Slack⁠, or Stack Overflow⁠

• Where to file issues:
  https://github.com/docker-library/gcc/issues⁠

• Maintained by:
  the Docker Community⁠

• Published image artifact details:
  repo-info repo's repos/gcc/ directory⁠ (history⁠)
  (image metadata, transfer size, etc)

• Image updates:
  official-images PRs with label library/gcc⁠
  official-images repo's library/gcc file⁠ (history⁠)

• Source of this description:
  docs repo's gcc/ directory⁠ (history⁠)

• 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 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 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 gcc:4.9 make

License

View license information⁠ for the software contained in this image.