Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Starting sibling containers
  • From: Julien Enoch <julien.enoch@xxxxxxxxxxxxxx>
  • Date: Wed, 29 Apr 2020 07:16:27 +0000
  • Accept-language: fr-FR, en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xjZ6hOakhPdikKm17ZK2lSBfkKDehaXU12OJaK3g/6w=; b=JdngEEIJoW3vbgS2NluHor/ZlHARAVEuOlXjU+1SxFKqIOVwK+cFHV6hH9Cw5REKo8OIQBUC2nYeswQsmeBGHAMjJj9j6+V/8LnP3YeJw7HF9marBAHnlEujcQHqgClrmodRXwTSupApTwPgVD4mKJ/zufo8Lw7XAr0jr3oY+gq6J/1B4ZcChx+NS02gY66hplMCcWFINFenmRAiKMZFSg4S91jc/w+Q/7ngAFzvfel25o/BSM7a/IBF2ksWgc5b3ADVV6V6HXdQaS7t9LQV0H90vOa3z0blgiaR97lOdHjaJfNA1KJrf6hpkEdNga0l6xnW+0cJTbe3y9P2OH9Fkw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=AKpajJg1KVbkniKCg8ig/YBGxQqhZ3iMhzndMWXAsiewUNCkvrImgdo9jEZS3SeTr3GGqHqrxF33PTWo337c3u340oPHNYqinznBNq90+NtdmFKk5q+WDzP5e9GHkW8/7+nS/m3Hs6pWyqBAqbI5bnUnfkJpA0adEHutvrkuHp5OYtbE/6ncIST8oz37KsputdJJTd9TbiwhTjMa/8Zd02MPnig6S6+JZq5iMnGjirrqMbtMP97lvsl77ApEM0GidztLohmGyaZyu+sD5aAWLMRfKVfn/pfId9ZwH1oHNqUhT0XWTD7Cmvlv8YfQubyrdEYKvFlL/CnNexayJXVCoA==
  • Delivered-to: cbi-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Thread-index: AQHWHXv8OE42563o+U6LnVe7PcKjZ6iOv0UAgADx8wA=
  • Thread-topic: [cbi-dev] Starting sibling containers

Hi Mikaël,

Thanks for this clarification.

Still, our Java library embeds the native (C) libraries for all the platforms we supports (x86, ARM, MacOS…).
Therefore, we need in a single Maven build to compile all the native libraries and to bundle them into a jar.
The current solution is to have Maven calling a Makefile which calls the various cross-compilation Docker containers to build the native libs, and then goes on with packaging and tests.
The great advantage of this, is that any user only needs to pre-install Docker (and SWIG) before to run a regular mvn command.

Do you see a solution to make this work in CBI with a custom pod template?


Le 28 avr. 2020 à 18:50, Mikael Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> a écrit :

My question:
Is it possible for a build in CBI to pull/start Docker containers on the fly, and if yes, how ?

No, it's not possible for security reasons: letting people mount the docker socket basically grants root access to the host.

If you want to run your builds in custom docker container, you can use custom pod templates (


Mikaël Barbero 
Team Lead - Release Engineering | Eclipse Foundation
🐦 @mikbarbero
Eclipse Foundation: The Platform for Open Innovation and Collaboration

cbi-dev mailing list
To unsubscribe from this list, visit

Back to the top