You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2019/12/13 06:40:59 UTC

[GitHub] [couchdb-docker] wohali opened a new issue #161: Work around qemu/ppc64le issue for debian buster

wohali opened a new issue #161: Work around qemu/ppc64le issue for debian buster
URL: https://github.com/apache/couchdb-docker/issues/161
 
 
   As mentioned in https://github.com/apache/couchdb-ci/issues/27 we are not presently able to build debian buster images for CouchDB CI use on ppc64. This will in turn limit our ability to build packages for that platform, which in turn will limit our ability to release Docker containers on that platform.
   
   The overriding reason to move the base image from stretch to buster is that buster [contains Spidermonkey 60](https://github.com/apache/couchdb/issues/1875) which is [coming to CouchDB 3.0](https://github.com/apache/couchdb/pull/2170), and at present, buster is the only supported Linux distro to ship pre-built binaries.
   
   Rather than go through the trouble of building SM60 for all the platforms (as we do for SM1.8.5 today) the simplest workaround is to special-case the Docker CouchDB 3.0 container to use stretch instead of buster for ppc64le (and continue to be on SM1.8.5 for now), which is fine.
   
   The fix is easy: a simple copy of the Dockerfile to Dockerfile.ppc64le with the FROM line changed, and a similar change downstream in the main Docker repo to reference the new Dockerfile specifically for ppc64le. This allows arm64v8 and amd64 at least to move forward with SM60 support, for the very large number of people using those platforms.
   
   Once the upstream qemu/buster issue is resolved, we can go back to a single Dockerfile for all platforms.
   
   A soon-to-follow PR will add the 3.0.0 prototype Dockerfiles.
   
   /cc @willholley 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services