-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow supporting multiple yocto branches #25
Comments
Hi,
So, we currently don't fetch the full git tree to keep the container sizes
down. If you would like to run other branches of toaster than the ones we
have custom containers for there is the --local option. For example:
this assumes you have checked out poky in `pwd` and switched to the branch
you are interested in.
docker run -it --rm -p 0.0.0.0:18000:8000 -v `pwd`:/workdir crops/toaster
--local
The --local flag tells the container to start up the toaster that is found
in /workdir/poky/bitbake/bin/toaster.
This mode is primarily aimed at toaster development, rather than usage.
This highlights the a couple of issues, however.
1)Toaster has not been consistent on how it is started up especially where
older versions are concerned. The current containers special case the
different versions we support, but there is not a generic solution.
2) The requirements for toaster have changed for the various releases. For
example, this is what happens when I try to run daisy using --local
"This program needs Django 1.5. Please install with
sudo pip install django==1.5"
The containers are not set up to handle this.
3) The versions of Django and South (deprecated and abandoned) that the
older versions of toaster were built with have not gotten security updates
in quite some time, which is worrisome...
…----
-brian
an intel employee
On Fri, Jun 2, 2017 at 6:38 AM, Yannick Koehler ***@***.***> wrote:
The docker container once run only propose the local yocto build in the
image or the tip of the same yocto branch. I would like to enable this
docker image to support more branches.
Yet, within the image if I go under /home/usersetup/poky and do git
checkout -b origin/ I get
***@***.***:/home/usersetup/poky$ git checkout -b daisy
origin/daisy
fatal: Cannot update paths and switch to branch 'daisy' at the same time.
Did you intend to checkout 'origin/daisy' which can not be resolved as
commit?
***@***.***:/home/usersetup/poky$ git fetch
error: cannot open .git/FETCH_HEAD: Permission denied
As such, I think the dockerfile need to fetch the origin fully to enable
retreiving more branches.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#25>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACkxjbeepBmUAsB-IyA5vhgrQaX5fAhtks5sABBIgaJpZM4NuS6g>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The docker container once run only propose the local yocto build in the image or the tip of the same yocto branch. I would like to enable this docker image to support more branches.
Yet, within the image if I go under /home/usersetup/poky and do git checkout -b origin/ I get
toasteruser@6b5c7e6985b2:/home/usersetup/poky$ git checkout -b daisy origin/daisy
fatal: Cannot update paths and switch to branch 'daisy' at the same time.
Did you intend to checkout 'origin/daisy' which can not be resolved as commit?
toasteruser@6b5c7e6985b2:/home/usersetup/poky$ git fetch
error: cannot open .git/FETCH_HEAD: Permission denied
As such, I think the dockerfile need to fetch the origin fully to enable retreiving more branches.
The text was updated successfully, but these errors were encountered: