wohali commented on issue #85: Provide and publish arm64 images
URL: https://github.com/apache/couchdb-docker/issues/85#issuecomment-429418332
 
 
   First off, thanks again for your help here. I am overloaded with other tasks 
at the moment, and additional platform support for Docker is low on the list.
   
   See https://github.com/apache/couchdb-docker/issues/68 for details, but 
roughly:
   
   1. Update the `couchdb-ci` repo to build a couchdbdev docker image for arm64 
that matches the configuration of the other nodes. This is an image that 
includes all of the prerequisites to build CouchDB. The scripts are pretty 
complete, but as you've noticed, we won't be able to install Erlang using the 
packages from Erlang Solutions - so the first step would be to enhance the 
scripts to build Erlang from scratch via an environment variable setting that 
we set by default for ARM. (There's a platform detect script that would be 
ideal for this). Put up a PR for this and we'll get it merged, and I'll push up 
the actual `couchdbdev/<name>` image to Docker Hub for us.
   1. Identify an arm64 host within the ASF's Jenkins machine list and start 
working with the main `Jenkinsfile` in `apache/couchdb` to run this build 
regularly. Any branch on the main repo starting with `jenkins-` will run that 
test file, so I'll create a branch called `jenkins-arm64` for you. Set your PR 
to merge against that branch. We can then re-trigger the branch regularly, 
until we can merge it to `master` where it will be run on every build of 
CouchDB.
   1. Once we have that arm64 build green - meaning all tests pass regularly & 
it's added to our regression testing so that we don't end up with undetected 
failures, we can then update the `couchdb-pkg` repo if necessary to correctly 
build an arm64 package. The pending change on `lintian` affects other builds as 
well, so I'll take care of that one.
   1. Then a PR against this repo to enable arm64 would be suitable.

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


With regards,
Apache Git Services

Reply via email to