From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] support OEQA inside container
Date: Thu, 12 Dec 2019 21:52:08 +0000 [thread overview]
Message-ID: <20191212215212.27089-1-git@andred.net> (raw)
Hi,
With these patches it is possible to run bitbake inside a docker
container and still successfully execute the OEQA tests that require
the target to talk to a temporary http server spawned on the machine
running bitake, e.g. using crops.
This wasn't possible so far because:
* we need to map a port from outside the container into the container
for the target to be able to reach the http server
* we need to pass the IP address of the docker host to the target,
e.g. in the OPKG repository URL, but we can't bind the http server
to that IP address, as the http server is running inside the container
with a different IP address - the bind would fail
To make this work, TEST_SERVER_IP needs to be set to the IP address of
the docker host, and the port that is mapped into the container can now
also be specified in TEST_SERVER_IP, similar to TEST_TARGET_IP
Cheers,
Andre'
next reply other threads:[~2019-12-12 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 21:52 André Draszik [this message]
2019-12-12 21:52 ` [PATCH 1/4] oeqa/utils/httpserver: allow to pass in listening port André Draszik
2019-12-12 21:52 ` [PATCH 2/4] oeqa/runtime/context.py: support listening port in TEST_SERVER_IP André Draszik
2019-12-12 21:52 ` [PATCH 3/4] oeqa/target/ssh oeqa/target/qemu: expose server listening port to tests André Draszik
2019-12-12 21:52 ` [PATCH 4/4] oeqa/runtime/apt dnf opkg: support running from within docker container André Draszik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191212215212.27089-1-git@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox