On 24/08/2016 18:03, "[email protected] on behalf of Barros Pena, Belen" <[email protected] on behalf of [email protected]> wrote:
> > >On 24/08/2016 17:12, "[email protected] on behalf of Barros >Pena, Belen" <[email protected] on behalf of >[email protected]> wrote: > >>Brian: send a link to a CROPS instance we can try and the document on how >>to run the Toaster Docker container > >Here come the links (thanks Brian): > >Toaster Docker containers: >https://hub.docker.com/r/crops/toaster-krogoth/ >https://hub.docker.com/r/crops/toaster-master/ > >Instructions: >https://github.com/crops/toaster-container I gave the container a go this morning, and I wanted to tell you all about it ... mainly for toaster manual writing purposes. First, I had to install Docker in Ubuntu 14.04. The Docker instructions looked very scary https://docs.docker.com/engine/installation/linux/ubuntulinux/ Then someone told me they have a magic script that automates all those steps https://www.digitalocean.com/community/tutorials/how-to-install-and-use-doc ker-compose-on-ubuntu-14-04 This works really well, but you do need to remember to add your user to the docker group before you do anything else sudo usermod -aG docker $(whoami) Then you have to log out and log back in for the group changes to take effect. Since I am behind a proxy, I had to edit the /etc/default/docker file to set http_proxy and https_proxy. I would have never managed this without help. Then I pulled the container I wanted to try using the command provided at https://hub.docker.com/r/crops/toaster-master/ To run it, I followed the instructions here https://github.com/crops/toaster-container I created a workdir as /home/<user>/toaster-workdir Then I run the run command in the readme file like this docker run -it --rm -p 127.0.0.1:18000:8000 -v /home/<user>/toaster-workdir:/toaster-workdir crops/toaster That made Docker pull a different container. I didn't realise that crops/toaster should have been crops/toaster-master in my case :/ So gave it another try with docker run -it --rm -p 127.0.0.1:18000:8000 -v /home/<user>/toaster-workdir:/toaster-workdir crops/toaster-master That failed saying the workdir directory didn't exist. So I deleted the /home/<user>/toaster-workdir directory and created /home/<user>/workdir instead. Then the run command as above worked like a charm, and the container came up. I was able to access the container from another computer at name_of_server_running_the_container:18000 I created a project with the master release and started a build. Sadly that failed during the cloning stage because I am behind a proxy, and I was told I would need to configure the proxy in the container. I have no idea how to do that. Then I thought I should try the local release instead. But once again, the build failed, this time with this message: Existing git repository at /home/usersetup/poky, but with different remotes ('origin http://git.yoctoproject.org/git/poky (fetch), origin http://git.yoctoproject.org/git/poky (push), ', expected 'git://git.yoctoproject.org/poky'). Toaster will not continue out of fear of damaging something. I stopped at this point, and wrote this email :) >From the experience so far, when writing the content for the manual, it might be handy to provide 1. Some instructions on how to easily install docker 2. What to do if you are behind a proxy I also have a couple of questions: 1. Does the workdir have to be called "workdir"? Or did I do something wrong? 2. Do we need to fix the issue with the local project builds? Cheers Belén > >Instructions for running tests (in progress): >https://wiki.yoctoproject.org/wiki/TipsAndTricks/TestingToasterWithContain >e >rs > > >-- >_______________________________________________ >toaster mailing list >[email protected] >https://lists.yoctoproject.org/listinfo/toaster -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
