consider building with golang-go on wily-arm64

Bug #1488669 reported by Michael Hudson-Doyle on 2015-08-25
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Wishlist
Kick In
Nominated for Trusty by Mathew Hodson

Bug Description

I'm not sure the process by which this should be decided, but there is a 'real' golang-go package on arm64 now and it should be possible to build docker with it.

(there is a real golang-go package on ppc64le too, but the cgo support isn't good enough to build docker)

Robie Basak (racb) wrote :

Are there any potential downsides to switching?

I guess it might reveal bugs in our go arm64 implementation.

Has gccgo been working out OK for docker? Might be worth checking what
upstream think, I guess.

Kick In (kick-d) on 2015-09-18
Changed in docker.io (Ubuntu):
assignee: nobody → Kick In (kick-d)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package docker.io - 1.6.2~dfsg1-1ubuntu4

---------------
docker.io (1.6.2~dfsg1-1ubuntu4) wily; urgency=medium

  * Add patches from upstream to fix some upgrade path bugs:
    - d/p/add-mutex-read-m_path.patch to fix vivid upgrade-path
    - d/p/stop-systemd-on-destroy.patch to fix leftover ".scope" fails
  * Add patches to fix Wily FTBFS:
    - d/p/ppc64el-wily.patch to fix ppc64le FTBFS on wily (LP: #1488668)
    - d/p/golang-1.5-wily.patch to fix FTBFS with golang-1.5 build on
      wily
  * arm64 support fixes for golang-go build (LP: #1488669):
    - d/p/libcontainer_arm64_syscall_dup2_to_dup3-c_changes.patch (LP:
      #1488669)
    - d/p/libcontainer_arm64_syscall_dup2_to_dup3-golang_changes.patch
      (LP: #1488669)
  * d/rules to build with golang-go on arm64 (LP: #1488669)
  * d/control to build with golang-go on arm64 (LP: #1488669)
  * Revert device-mapper-cleanup.patch dropped with an new one:
    d/p/device-mapper-cleanup2.patch

 -- Pierre-André MOREY <email address hidden> Fri, 18 Sep 2015 14:50:57 +0200

Changed in docker.io (Ubuntu):
status: New → Fix Released

Hello Michael, or anyone else affected,

Accepted docker.io into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/docker.io/1.6.2~dfsg1-1ubuntu4~14.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Changed in docker.io (Ubuntu):
importance: Undecided → Wishlist
tags: removed: verification-needed
Van Duc Uy (vducuy) wrote :

Docker failed to run on ARM64

amcc@ubuntu:~$ sudo docker -d
INFO[0000] +job serveapi(unix:///var/run/docker.sock)
INFO[0000] Listening for HTTP on unix (/var/run/docker.sock)
INFO[0000] +job init_networkdriver()
INFO[0000] -job init_networkdriver() = OK (0)
INFO[0001] Loading containers: start.

INFO[0001] Loading containers: done.
FATA[0001] Shutting down daemon due to errors: function not implemented
amcc@ubuntu:~$

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers