eine

@wagoodman, in case you want to not only build the tool for multiple architectures with goreleaser, but also build (and probably test) docker images for them (on the same amd64...

@AA122AA, since this tool is written in golang, I believe that the complexity is not related to building it for ARM (which should work OOTB). Instead, the difficulty relies on...

@apulache, `dive` on x86_64 might already work for inspecting docker images for foreign architectures. Did you try it?

I believe that this issue is precisely to request better/complete support; i.e. not to be constrained to input/outputs or to a single wire/signal. In the context of Wishbone and AXI,...

> We are working on a new version of icestudio (now only in design and concepts) and this concept will be very usefull and interesting. In the current version will...

That sounds really interesting. Is there any public discussion about the requirements, frameworks and/or proposed architecture? IMHO, given the limited human resources, it would be interesting to allow the community...

> Right now we are stabilizing the dev branch and we want to add a new feature of plugins I'm looking forward to that! I cloned the repository, but there...

@robbuckley, what do you mean with 'the local filesystem' in the context of running dive in a docker container? I'd like it to be the host where the container is...

@robbuckley, the point is that, when `dive` is started as follows: `docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock wagoodman/dive:latest ` executing `docker cp CONTAINER:SRC_PATH DEST_PATH` internally will place files in `DEST_PATH`...

> export a single file onto your host to you can inspect the contents In my case, I don't want to export it in order to inspect it, but to...