AuroraMiddleware/protobuf
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity
2af13f077a
protobuf/protoc-artifacts/Dockerfile

56 lines
2.1 KiB
Docker
Raw Normal View History

protoc-artifacts: Update centos base from 6.6 to 6.9 This avoids the need to use "yum update && yum upgrade" in the container to be able to contact GitHub, which requires TLS 1.2[1]. I have verified that binaries built with this container still run in the previous container; no errors like "/lib64/libc.so.6: version `GLIBC_2.14' not found", which occur if using too new of a glibc when compiling. CentOS 6.6 has glibc version 2.12 release 1.209.el6. CentOS 6.9 has glibc version 2.12 release 1.149.el6. Both would upgrade to release 1.212.el6 via "yum update && yum upgrade". 1. https://githubengineering.com/crypto-deprecation-notice/
2018-07-07 00:37:52 +00:00
FROM centos:6.9
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
RUN yum install -y git \
tar \
wget \
make \
autoconf \
curl-devel \
unzip \
automake \
libtool \
glibc-static.i686 \
glibc-devel \
protoc-artifacts: Avoid storing temporary files and use fewer layers This is just better Dockerfile hygene as it produces smaller resulting images with fewer useless files.
2018-03-29 00:06:47 +00:00
glibc-devel.i686 \
&& \
yum clean all
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
# Install Java 8
RUN wget -q --no-cookies --no-check-certificate \
protoc-artifacts: Bump JDK to 8u131 The update 45 download process no longer works, as it requires a login to access the old build.
2017-07-05 20:13:51 +00:00
--header "Cookie: gpw_e24=http%3A%2F%2Fwww.oracle.com%2F; oraclelicense=accept-securebackup-cookie" \
"http://download.oracle.com/otn-pub/java/jdk/8u131-b11/d54c1d3a095b4ff2b6607d096fa80163/jdk-8u131-linux-x64.tar.gz" \
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
-O - | tar xz -C /var/local
protoc-artifacts: Bump JDK to 8u131 The update 45 download process no longer works, as it requires a login to access the old build.
2017-07-05 20:13:51 +00:00
ENV JAVA_HOME /var/local/jdk1.8.0_131
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
ENV PATH $JAVA_HOME/bin:$PATH
# Install Maven
Fix maven links. [ci skip] Change-Id: Ibefbdf441d932c5751235c635244450d7cbacc53
2016-07-22 23:23:48 +00:00
RUN wget -q http://apache.cs.utah.edu/maven/maven-3/3.3.9/binaries/apache-maven-3.3.9-bin.tar.gz -O - | \
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
tar xz -C /var/local
Fix maven path. Change-Id: I252d7a644a9e4064a9f1a816a2be3f25f37b4c43
2016-07-24 02:43:03 +00:00
ENV PATH /var/local/apache-maven-3.3.9/bin:$PATH
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
Updated Docker setup to use GCC 4.8 Now that we depend on C++11, we need at least GCC 4.8 instead of 4.7. This change updates the Docker setup to continue using CentOS 6.6 but with GCC 4.8. I also added libm to the whitelist for dynamically linked libraries for the ARM64 protoc binary.
2018-07-06 19:38:14 +00:00
# Install GCC 4.8 to support -static-libstdc++
RUN wget http://people.centos.org/tru/devtools-2/devtools-2.repo -P /etc/yum.repos.d && \
bash -c 'echo "enabled=1" >> /etc/yum.repos.d/devtools-2.repo' && \
bash -c "sed -e 's/\$basearch/i386/g' /etc/yum.repos.d/devtools-2.repo > /etc/yum.repos.d/devtools-i386-2.repo" && \
sed -e 's/testing-/testing-i386-/g' -i /etc/yum.repos.d/devtools-i386-2.repo && \
Fix protoc release (#5615) * Fix protoc release * Update Dockerfile to include libatomic
2019-01-23 18:55:36 +00:00
rpm --rebuilddb
RUN yum install -y devtoolset-2-gcc \
devtoolset-2-gcc-c++ \
devtoolset-2-binutils \
devtoolset-2-libstdc++-devel \
devtoolset-2-libatomic-devel \
libatomic \
devtoolset-2-gcc.i686 \
devtoolset-2-gcc-c++.i686 \
devtoolset-2-binutils.i686 \
devtoolset-2-libstdc++-devel.i686 \
devtoolset-2-libatomic-devel.i686 \
libatomic.i686 && \
protoc-artifacts: Avoid storing temporary files and use fewer layers This is just better Dockerfile hygene as it produces smaller resulting images with fewer useless files.
2018-03-29 00:06:47 +00:00
yum clean all
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
protoc-artifacts: Use ENTRYPOINT to enable devtoolset-1.1 ENTRYPOINT is used even when other commands are specified on the "docker run" command line. This allows running one-off commands in the docker image (especially combined with volume binding with the host) with the correct environment variables.
2018-03-29 00:15:36 +00:00
COPY scl-enable-devtoolset.sh /var/local/
Dockerfile for building protoc on Centos 6.6
2015-05-12 00:13:59 +00:00
# Start in devtoolset environment that uses GCC 4.7
protoc-artifacts: Use ENTRYPOINT to enable devtoolset-1.1 ENTRYPOINT is used even when other commands are specified on the "docker run" command line. This allows running one-off commands in the docker image (especially combined with volume binding with the host) with the correct environment variables.
2018-03-29 00:15:36 +00:00
ENTRYPOINT ["/var/local/scl-enable-devtoolset.sh"]
Reference in New Issue Copy Permalink