Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-2255

bigtop/deploy:ubuntu-15.04 image does not support ppc64le

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 1.0.0
    • Fix Version/s: 1.0.1, 1.1.0
    • Component/s: build, docker
    • Labels:
      None

      Activity

      Hide
      evans_ye Evans Ye added a comment -

      Got error building on Amazon Linux:

      [ubuntu-15.04-ppc64le]# ./build.sh
      Sending build context to Docker daemon 57.86 kB
      Step 1 : FROM bigtop/puppet:ubuntu-15.04-ppc64le
      ubuntu-15.04-ppc64le: Pulling from bigtop/puppet
      20c927e6d3a1: Pull complete
      6ea744063e69: Pull complete
      b7f59fb0f3e7: Pull complete
      7d1f72ace99e: Pull complete
      46bd05ffeb5d: Pull complete
      d7e187195aac: Pull complete
      f71075f161e0: Pull complete
      Digest: sha256:5016e169a61f5f6103f67e83d47042f53d85d437f8e5c47bae47c9289fc4ccc1
      Status: Downloaded newer image for bigtop/puppet:ubuntu-15.04-ppc64le
       ---> f71075f161e0
      Step 2 : MAINTAINER Amir Sanjar
       ---> Running in 0cd1fc51ccb7
       ---> d8a326f13b01
      Removing intermediate container 0cd1fc51ccb7
      Step 3 : COPY bigtop_toolchain /etc/puppet/modules/bigtop_toolchain
       ---> 0f55505c4578
      Removing intermediate container 2cf5835bd51d
      Step 4 : RUN apt-get update &&     apt-get install -y openssh-server vim &&     mkdir -p /var/run/sshd &&     sed -i.bak 's/requiretty/!requiretty/' /etc/sudoers &&     mkdir -p /root/.ssh &&     chmod 0700 /root/.ssh &&     wget http://github.com/mitchellh/vagrant/raw/master/keys/vagrant.pub --no-check-certificate -O /root/.ssh/authorized_keys &&     chmod 0600 /root/.ssh/authorized_keys &&     puppet apply -e "include bigtop_toolchain::puppet-modules"
       ---> Running in acdedf3cd08e
      exec format error
      [8] System error: exec format error
      

      I guess that's because I need to build this on a ppc64le machine?

      Show
      evans_ye Evans Ye added a comment - Got error building on Amazon Linux: [ubuntu-15.04-ppc64le]# ./build.sh Sending build context to Docker daemon 57.86 kB Step 1 : FROM bigtop/puppet:ubuntu-15.04-ppc64le ubuntu-15.04-ppc64le: Pulling from bigtop/puppet 20c927e6d3a1: Pull complete 6ea744063e69: Pull complete b7f59fb0f3e7: Pull complete 7d1f72ace99e: Pull complete 46bd05ffeb5d: Pull complete d7e187195aac: Pull complete f71075f161e0: Pull complete Digest: sha256:5016e169a61f5f6103f67e83d47042f53d85d437f8e5c47bae47c9289fc4ccc1 Status: Downloaded newer image for bigtop/puppet:ubuntu-15.04-ppc64le ---> f71075f161e0 Step 2 : MAINTAINER Amir Sanjar ---> Running in 0cd1fc51ccb7 ---> d8a326f13b01 Removing intermediate container 0cd1fc51ccb7 Step 3 : COPY bigtop_toolchain /etc/puppet/modules/bigtop_toolchain ---> 0f55505c4578 Removing intermediate container 2cf5835bd51d Step 4 : RUN apt-get update && apt-get install -y openssh-server vim && mkdir -p / var /run/sshd && sed -i.bak 's/requiretty/!requiretty/' /etc/sudoers && mkdir -p /root/.ssh && chmod 0700 /root/.ssh && wget http: //github.com/mitchellh/vagrant/raw/master/keys/vagrant.pub --no-check-certificate -O /root/.ssh/authorized_keys && chmod 0600 /root/.ssh/authorized_keys && puppet apply -e "include bigtop_toolchain::puppet-modules" ---> Running in acdedf3cd08e exec format error [8] System error: exec format error I guess that's because I need to build this on a ppc64le machine?
      Hide
      oflebbe Olaf Flebbe added a comment -

      Of course, docker is not an emulator.

      Created Docker-Deploy-ppc64le

      Show
      oflebbe Olaf Flebbe added a comment - Of course, docker is not an emulator. Created Docker-Deploy-ppc64le
      Hide
      oflebbe Olaf Flebbe added a comment -

      Amir Sanjar: Could you please have a look into BIGTOP-2228? Is tini available for ppc64le as well?

      Show
      oflebbe Olaf Flebbe added a comment - Amir Sanjar : Could you please have a look into BIGTOP-2228 ? Is tini available for ppc64le as well?
      Hide
      oflebbe Olaf Flebbe added a comment -

      OK, let tini be a new JIRA , This patch LGTM, +1

      Show
      oflebbe Olaf Flebbe added a comment - OK, let tini be a new JIRA , This patch LGTM, +1
      Hide
      oflebbe Olaf Flebbe added a comment -

      Oops the CI for ppc64le is broken right now. Docker does not start any more ;-(

      Show
      oflebbe Olaf Flebbe added a comment - Oops the CI for ppc64le is broken right now. Docker does not start any more ;-(
      Hide
      oflebbe Olaf Flebbe added a comment -

      Pushed, but new image is not generated. Will have to wait until this is fixed

      Show
      oflebbe Olaf Flebbe added a comment - Pushed, but new image is not generated. Will have to wait until this is fixed
      Hide
      Ayappan Ayappan added a comment -

      There is an internal bug raised within IBM for this docker problem after a abrupt host shutdown.
      Workaround
      ---------------
      docker daemon when comes up, it tries to cleanup oldcontainers.
      This is not happening successfully with libcontainer driver.
      The cleanup happens successfully when we start docker daemon with lxc driver

      apt-get install lxc
      docker -d -D -e lxc --log-level=info

      [ we can kill this docker daemon]
      and next time we can start docker normally using
      service docker start

      Permanent fix to this is to use docker built with latest gccgo and linked to glibc2.21
      A new docker binary with the required fix is hosted in the following repo

      1. echo "deb http://pokgsa.ibm.com/projects/d/docker/apt-repo/trusty trusty main" > /etc/apt/sources.list.d/trusty-docker.list
      2. apt-get update
      3. apt-get install docker.io
      Show
      Ayappan Ayappan added a comment - There is an internal bug raised within IBM for this docker problem after a abrupt host shutdown. Workaround --------------- docker daemon when comes up, it tries to cleanup oldcontainers. This is not happening successfully with libcontainer driver. The cleanup happens successfully when we start docker daemon with lxc driver apt-get install lxc docker -d -D -e lxc --log-level=info [ we can kill this docker daemon] and next time we can start docker normally using service docker start Permanent fix to this is to use docker built with latest gccgo and linked to glibc2.21 A new docker binary with the required fix is hosted in the following repo echo "deb http://pokgsa.ibm.com/projects/d/docker/apt-repo/trusty trusty main" > /etc/apt/sources.list.d/trusty-docker.list apt-get update apt-get install docker.io

        People

        • Assignee:
          asanjar Amir Sanjar
          Reporter:
          asanjar Amir Sanjar
        • Votes:
          0 Vote for this issue
          Watchers:
          4 Start watching this issue

          Dates

          • Due:
            Created:
            Updated:
            Resolved:

            Development