yes, That's from the change we did on how we interpret the webport argument and whether it binds to all interfaces (old behaviour) or only to localhost (new behaviour). It's the same whether we run toaster from w/in a container or not. -b
On Fri, Aug 26, 2016 at 5:59 AM, Barros Pena, Belen < [email protected]> wrote: > > > On 25/08/2016 17:26, "Brian Avery" <[email protected]> wrote: > > >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 > > Just a small correction. The instructions in GitHub say to run > > docker run -it --rm -p 127.0.0.1:18000:8000 -v > /home/myuser/workdir:/workdir crops/toaster-master > > > But in order to access the container from a different machine I had to run > > docker run -it --rm -p 0.0.0.0:18000:8000 -v /home/myuser/workdir:/workdir > crops/toaster-master > > > Cheers > > Belén > >
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
