- 23 Jan, 2019 1 commit
-
-
Hao Nguyen authored
* Fix protoc release * Update Dockerfile to include libatomic
-
- 17 Jul, 2018 2 commits
-
-
Eric Anderson authored
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/
-
Adam Cozzette authored
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.
-
- 07 Jul, 2018 1 commit
-
-
Eric Anderson authored
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/
-
- 06 Jul, 2018 1 commit
-
-
Adam Cozzette authored
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.
-
- 29 Mar, 2018 3 commits
-
-
Eric Anderson authored
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.
-
Eric Anderson authored
This is just better Dockerfile hygene as it produces smaller resulting images with fewer useless files.
-
Eric Anderson authored
It is a bad idea to check out code into the docker image, as it will be out-of-date. It is better to have the image just be the environment, and let any scripts that need source check them out themselves. This fixes #4419 in that it allows the image to build again, albeit users would need to use wget to grab the source of the version of protobuf they wish.
-
- 05 Jul, 2017 1 commit
-
-
Eric Anderson authored
The update 45 download process no longer works, as it requires a login to access the old build.
-
- 11 May, 2017 1 commit
-
-
Łukasz Strzałkowski authored
This is a workaround (https://github.com/moby/moby/issues/10180#issuecomment-190429512) the docker issue (https://github.com/moby/moby/issues/10180) which breaks protoc-artifacts build process with following error ```Rpmdb checksum is invalid: dCDPT(pkg checksums): devtoolset-1.1-elfutils.x86_64 0:0.154-6.el6 - u The command '/bin/sh -c yum clean all && yum install -y devtoolset-1.1 devtoolset-1.1-libstdc++-devel devtoolset-1.1-libstdc++-devel.i686' returned a non-zero code: 1``` https://github.com/moby/moby/issues/10180#issuecomment-190429512
-
- 24 Jul, 2016 1 commit
-
-
Feng Xiao authored
Change-Id: I252d7a644a9e4064a9f1a816a2be3f25f37b4c43
-
- 22 Jul, 2016 1 commit
-
-
Feng Xiao authored
[ci skip] Change-Id: Ibefbdf441d932c5751235c635244450d7cbacc53
-
- 12 May, 2015 1 commit
-
-
Kun Zhang authored
-