We need Debian Jessie to build packages with systemd support.

  1. Upgrade ci server to 3.16 kernel
  2. Install docker
  3. build container
  4. adapt jenkins job

Comments

helmo created an issue. See original summary.

helmo’s picture

Kernel was installed from Wheezy-backports, docker from https://docs.docker.com/installation/debian/

helmo’s picture

Started with a Docker file on the 7.x-3.x branch in http://github.com/aegir-project/aegir_jenkins_scripts.git

jenkins@zeus$ docker build .
Sending build context to Docker daemon 15.36 kB
Step 0 : FROM joeyh/debian-stable-amd64
 ---> 01d1d78001da
Step 1 : RUN apt-get update
 ---> Running in 69256344d44f
[8] System error: write /dev/cgroup/docker/69256344d44f2d0df63235590e1f26653dcb3e61affe3c0fb8100278a081758f/cgroup.procs: no space left on device
jenkins@zeus$ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
535020c3e8ad: Pull complete 
af340544ed62: Already exists 
library/hello-world:latest: The image you are pulling has been verified. Important: image verification is a tech preview feature and should not be relied on to provide security.
Digest: sha256:d5fbd996e6562438f7ea5389d7da867fe58e04d581810e230df4cc073271ea52
Status: Downloaded newer image for hello-world:latest
WARNING: Your kernel does not support memory swappiness capabilities, memory swappiness discarded.
Error response from daemon: Cannot start container 0ecfcae485a362fffcbf40e26db61356be62a8093f8bcea5dc37147f1a5a47e0: [8] System error: write /dev/cgroup/docker/0ecfcae485a362fffcbf40e26db61356be62a8093f8bcea5dc37147f1a5a47e0/cgroup.procs: no space left on device
helmo’s picture

Issue summary: View changes
helmo’s picture

ergonlogic’s picture

Couldn't we use vagrant to build the packages?

helmo’s picture

Yes, that should also work ;)
Just a matter of passing in the gpg key and getting the package out.

ergonlogic’s picture

Isn't the GPG key to upload to the repo? What else do we need the generated .debs for? If we build them anywhere under /vagrant, they should be available to the host without much more work.

helmo’s picture

Docker run hello-world now seems to run OK, after https://www.drupal.org/node/2582969

helmo’s picture

Status: Active » Needs review

I updated our build job: http://ci.aegirproject.org/view/Debian%20dev%20builds/job/D_aegir-debian...

cd aegir_jenkins_scripts/buildenv-debian-jessie; 
./build_docker.sh

cd ..
./check_reprepro_upload.sh

TODO:

  • remove the provision and hostmaster git checkouts from the jenkins job. It's all in the container now.
  • See if we still want jenkins to also archive the packages
helmo’s picture

Darn not OK.

Docker was having trouble revolving DNS....
Used this http://serverfault.com/a/642984 to get it back up.

Now I'm still having trouble installing the packages:

==> default:  Aegir install profile: hostmaster
==> default: 
==> default: Do you really want to proceed with the install (y/n): y
==> default: Enabling hosting-queued daemon
==> default: The drush command '@hostmaster pm-enable hosting_queued' could not be    [error]
==> default: found.  Run `drush cache-clear drush` to clear the commandfile cache
==> default: if you have installed new extensions.
==> default: A Drupal installation directory could not be found                       [error]
==> default: dpkg: error processing package aegir3-hostmaster (--configure):
==> default:  subprocess installed post-installation script returned error exit status 1
==> default: dpkg: dependency problems prevent configuration of aegir3:
==> default:  aegir3 depends on aegir3-hostmaster (>= 3.1+.1829b19); however:
==> default:   Package aegir3-hostmaster is not configured yet.
==> default: 

After the confirmation from hostmaster-install it just stops??? The hosting_queued not being found is correct as the hostmaster platform has not even been build.

But why?

In an attempt to debug I added another testcase,
one that installs the debs with the extra DPKG_DEBUG option.

The added bonus is that I already wanted to have a test witch replicates the instructions from http://www.aegirproject.org/ as closely as possible.

helmo’s picture

I tried the D_aegir3-debian-test-unstable test with our stable debian repo(3.1 version) ... same problem.

So that should mean it's not a docker problem ... just an install on debian.

I also tried wheezy instead of jessie ... same problem.

helmo’s picture

Finally after adding some debug code to provision last night I found the reason why installs are failing.

Somehow this error was not printed.

Returned from hook drush_provision_drupal_post_provision_verify [1.99    [debug]
sec, 6.92 MB]
Command dispatch complete [1.99 sec, 6.92 MB]                           [notice]
Peak memory usage was 8.59 MB [1.99 sec, 6.92 MB]                       [memory]
Caught drush error, ending drush_provision_hostmaster_install [1.99      [debug]
sec, 6.92 MB]
Array                                                                    [debug]
(
    [PROVISION_DB_CONNECT_FAIL] => Array
        (
            [0] => SQLSTATE[28000] [1045] Access denied for user
'debian-sys-maint'@'localhost' (using password: YES)
        )

    [PROVISION_CONNECT_DB_FAILED] => Array
        (
            [0] => Unable to connect to database server.
        )

)
 [1.99 sec, 6.92 MB]
Returned from hook drush_provision_hostmaster_install [1.99 sec, 6.93    [debug]

full log: http://ci.aegirproject.org/view/Debian%20dev%20builds/job/D_aegir3-debia...

helmo’s picture

Status: Needs review » Fixed

Fixed I guess .. has been running OK for while now.

http://ci.aegirproject.org/view/Debian%20dev%20builds/job/D_aegir-debian...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.