Hello,
Situation with running Docker containers inside the official Docker-based LAVA setup (https://git.lavasoftware.org/lava/pkg/docker-compose) was already discussed at least once recently.
LAVA starts to offer more and more convenient usages of Docker containers to extend its functionality (e.g. https://connect.linaro.org/resources/ltd20/ltd20-304/), and people start to leverage it. For docker-compose based setup, that effectively means running Docker containers inside the docker-compose, and that currently doesn't work.
Another reason for raising this matter again are the apparent plans to migrate components of the production LAVA setup as run by Linaro (https://validation.linaro.org/) to Docker-based setup. The concern is that if Docker-in-Docker scenario is not explicitly accounted and planned for, then there will be a regression due to this switchover.
So, I posted https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/7 with more detailed discussion, and would be ready to follow up with a patch (we just need to decide what kind of patch, please the proposed options there).
On Thu, 25 Jun 2020 at 14:01, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello,
Situation with running Docker containers inside the official Docker-based LAVA setup (https://git.lavasoftware.org/lava/pkg/docker-compose) was already discussed at least once recently.
LAVA starts to offer more and more convenient usages of Docker containers to extend its functionality (e.g. https://connect.linaro.org/resources/ltd20/ltd20-304/), and people start to leverage it. For docker-compose based setup, that effectively means running Docker containers inside the docker-compose, and that currently doesn't work.
Another reason for raising this matter again are the apparent plans to migrate components of the production LAVA setup as run by Linaro (https://validation.linaro.org/) to Docker-based setup. The concern is that if Docker-in-Docker scenario is not explicitly accounted and planned for, then there will be a regression due to this switchover.
We won't migrate until we have a working setup. So you can sleep peacefully now :)
milosz
So, I posted https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/7 with more detailed discussion, and would be ready to follow up with a patch (we just need to decide what kind of patch, please the proposed options there).
-- Best Regards, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users
On Thu, 25 Jun 2020 14:07:40 +0100 Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Thu, 25 Jun 2020 at 14:01, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello,
Situation with running Docker containers inside the official Docker-based LAVA setup (https://git.lavasoftware.org/lava/pkg/docker-compose) was already discussed at least once recently.
LAVA starts to offer more and more convenient usages of Docker containers to extend its functionality (e.g. https://connect.linaro.org/resources/ltd20/ltd20-304/), and people start to leverage it. For docker-compose based setup, that effectively means running Docker containers inside the docker-compose, and that currently doesn't work.
Another reason for raising this matter again are the apparent plans to migrate components of the production LAVA setup as run by Linaro (https://validation.linaro.org/) to Docker-based setup. The concern is that if Docker-in-Docker scenario is not explicitly accounted and planned for, then there will be a regression due to this switchover.
We won't migrate until we have a working setup. So you can sleep peacefully now :)
That's reassuring, thanks! If only we had a spec for "working setup". Then we'd go thru it and added any missing bits to make it into "fully working setup", for anyone having experience with IT knowing that "fully working setup" and "working setup" are 2 different things, akin to the old proverb of "the best is the enemy of the good" ;-).
In that regard, I posted a next ticket, https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/8, an issue in which I'm sure wouldn't be overlooked anyway ;-).
milosz
So, I posted https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/7 with more detailed discussion, and would be ready to follow up with a patch (we just need to decide what kind of patch, please the proposed options there).
On Thu, 25 Jun 2020 at 15:29, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
On Thu, 25 Jun 2020 14:07:40 +0100 Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Thu, 25 Jun 2020 at 14:01, Paul Sokolovsky paul.sokolovsky@linaro.org wrote:
Hello,
Situation with running Docker containers inside the official Docker-based LAVA setup (https://git.lavasoftware.org/lava/pkg/docker-compose) was already discussed at least once recently.
LAVA starts to offer more and more convenient usages of Docker containers to extend its functionality (e.g. https://connect.linaro.org/resources/ltd20/ltd20-304/), and people start to leverage it. For docker-compose based setup, that effectively means running Docker containers inside the docker-compose, and that currently doesn't work.
Another reason for raising this matter again are the apparent plans to migrate components of the production LAVA setup as run by Linaro (https://validation.linaro.org/) to Docker-based setup. The concern is that if Docker-in-Docker scenario is not explicitly accounted and planned for, then there will be a regression due to this switchover.
We won't migrate until we have a working setup. So you can sleep peacefully now :)
That's reassuring, thanks! If only we had a spec for "working setup". Then we'd go thru it and added any missing bits to make it into "fully working setup", for anyone having experience with IT knowing that "fully working setup" and "working setup" are 2 different things, akin to the old proverb of "the best is the enemy of the good" ;-).
'fully working' is a bit too much to ask I'm afraid :P
In that regard, I posted a next ticket, https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/8, an issue in which I'm sure wouldn't be overlooked anyway ;-).
Thanks, much appreciated!
milosz
milosz
So, I posted https://git.lavasoftware.org/lava/pkg/docker-compose/-/issues/7 with more detailed discussion, and would be ready to follow up with a patch (we just need to decide what kind of patch, please the proposed options there).
-- Best Regards, Paul
Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#%21/linaroorg - http://www.linaro.org/linaro-blog
lava-users@lists.lavasoftware.org
-
Milosz Wasilewski -
Paul Sokolovsky