I'm not sure how to go about this one.  I've tried the latest version of devtoolset-4-toolchain-docker, devtoolset-4-toolchain-docker-4-9.2-x86_64.tar.gz, but that has still the old version of gcc:

bash-4.2$ gcc --version
gcc (GCC) 5.2.1 20150902 (Red Hat 5.2.1-2)

But I don't think there's anything to change in the Dockerfile:

RUN yum-config-manager --enable rhel-server-rhscl-7-rpms && \
    yum-config-manager --enable rhel-7-server-optional-rpms && \
    yum-config-manager --disable epel >/dev/null || : && \
    yum install -y --setopt=tsflags=nodocs devtoolset-4-gcc devtoolset-4-gcc-c++ devtoolset-4-gcc-gfortran devtoolset-4-gdb && \
    yum clean all -y

so it seems that this should pull in the newest version of devtoolset-4-gcc from rhel-server-rhscl-7-rpms or rhel-7-server-optional-rpms.  Perhaps devtoolset-4-gcc-5.3.1-4.el7 isn't in those repos yet?

Honza, would you know more?

hhorak seems to be on PTO; trying someone else ;).

Hi,

newer gcc package is not inside these repositories. See

dhcp-24-140:rzima ~ $  repoquery --repoid='rz' --repofrompath=rz,http://pulp.dist.prod.ext.phx2.redhat.com/content/dist/rhel/server/7/7Server/x86_64/rhscl/1/os/ -q devtoolset-4-gcc*
devtoolset-4-gcc-0:5.2.1-2.2.el7.x86_64
devtoolset-4-gcc-c++-0:5.2.1-2.2.el7.x86_64
devtoolset-4-gcc-gdb-plugin-0:5.2.1-2.2.el7.x86_64
devtoolset-4-gcc-gfortran-0:5.2.1-2.2.el7.x86_64
devtoolset-4-gcc-plugin-devel-0:5.2.1-2.2.el7.x86_64
dhcp-24-140:rzima ~ $  repoquery --repoid='rz' --repofrompath=rz,http://download.lab.bos.redhat.com/rel-eng/updates/RHEL-7.2-20160322.3/compose/Server-optional/x86_64/os/ -q devtoolset-4-gcc*

Rebuild will be needed after update.

Regards,
Radek

Thanks.  Seems that a pure rebuild helped:
$ docker run -i -t a6d5720f4795 gcc --version
gcc (GCC) 5.3.1 20160212 (Red Hat 5.3.1-4)

Verified for build rhscl/devtoolset-4-toolchain-rhel7:4-9.5.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1181