On Thu, Apr 14, 2016 at 5:40 PM Nicholas McCarthy
wrote:
> Yeah, this is one of the things I like most about Dockerfiles... the self
> documenting aspect. However... have you noticed how many times you end up
> dealing with Docker images apart from their Dockerfiles? For a lot of
> useful image
and then there's this
https://github.com/docker/docker/issues/12053
I'm not even sure what version of Docker I used when I did the compression
thing... it wasn't 1.10.
Cheers,
Nick M.
On Thu, Apr 14, 2016 at 8:40 PM Nicholas McCarthy
wrote:
> Yeah, this is one of the things I like most abo
Yeah, this is one of the things I like most about Dockerfiles... the self
documenting aspect. However... have you noticed how many times you end up
dealing with Docker images apart from their Dockerfiles? For a lot of
useful images, it's difficult (maybe impossible?) to track the Dockerfile
down.
On Thu, Apr 14, 2016 at 3:54 PM Nicholas McCarthy
wrote:
> Three points to make about this OOT Docker example.
> 1) Everything you're doing manually here can be accomplished using
> pybombs2... and pybombs2 makes itself quite amenable to existing within the
> Docker image both as an interface to
Three points to make about this OOT Docker example.
1) Everything you're doing manually here can be accomplished using
pybombs2... and pybombs2 makes itself quite amenable to existing within the
Docker image both as an interface to what's already installed on the image
and a handy way to install ne
>
> I think it would be really helpful for the GNU Radio project to support a
>> standard, basic gnuradio docker install with uhd and grc enabled as well as
>> an example or two to demonstrate sane ways to run OOT modules on top of
>> that image. As Ben mentioned, Docker seems like a pretty energy
Having almost no experience with Docker myself, I unfortunately don't have
much in the way of worthwhile technical input on this.
That said, I really do want to encourage this conversation. Installation of
GNU Radio on one machine can be a pain for many people, and doing it on
many machines over a
Keep in mind the automated build service of hub.docker.com! For those
who don't know how it works:
It is connected to the github repo and rebuilds after each new commit
the needed images (or layers) automatically.
As well, it would be possible to build automatically images for each
release of gnura
On Fri, Apr 8, 2016 at 8:09 AM, Stefan Wunsch wrote:
> Regarding running the GUI: In the readme I've included the commands for
> X forwarding (that's your approach). Works fine on my machine! The VNC
> approach targets especially windows users.
>
I've had success running GRC and QT-based GNU Ra
On Fri, Apr 8, 2016 at 6:12 AM, Ben Hilburn wrote:
> It seems like Docker could make it much easier for us to support a variety
> of operating systems - although the user would still need to install
> Docker, itself. Presumably that's easier than earlier containerized models,
> though (e.g., VMs
I think (but I am not totally sure) that you can target multiple cores
from a single container. So the -j option should work on your local
machine. But not on hub.docker.com, because you have only one core on
the server machine.
Greetings
On 04/08/2016 05:08 PM, Kevin Hofschröer wrote:
> Also, is
Hi,
That's true for now, but ubuntu's repos aren't made for developing. The
repos are just too old within a few month. And then recent (or self
developed) OOTs won't work.
Regarding running the GUI: In the readme I've included the commands for
X forwarding (that's your approach). Works fine on my
Also, is there a reason not to use the "-j" option in a Dockerfile?
Kevin
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Hello Stefan and all,
I also recently experimented with GR and Docker and at least got it working so
far.
My approach was different in that I used the ubuntu:16.04 base image where
gnuradio v3.7.9.1 (so pretty new) is available pre-compiled in the official
ubuntu repositories.
Of course that ap
Thanks for the responses, Stefan and Nick.
It seems like Docker could make it much easier for us to support a variety
of operating systems - although the user would still need to install
Docker, itself. Presumably that's easier than earlier containerized models,
though (e.g., VMs).
Cheers,
Ben
__
Hey,
Using hardware with docker containers is pretty easy. Just use the
--device flag and (effectively) share a folder/file of your host with
the container or use the --net=host flag to share the network
connection. Basically, that's all!
And Nick Foster is right, there should be almost no overhe
Hi Stefan -
This is really cool! Thanks so much for sharing your images and for posting
instructions. It looks like a number of people have started playing with
GNU Radio containers - I recognize some of the other names that have
publicly shared images (e.g., Nick Foster aka 'bistromath'). We chat
On Thu, Apr 7, 2016, 3:48 PM Ben Hilburn wrote:
>
> What was your experience like when it came to using the RTL dongle? Was
> there any complexity there? If you have hardware that can stream at higher
> rates, I'd be interested in how those perform in the container, as well.
>
Performance is, fo
18 matches
Mail list logo
