r-cheologist

Just ran into this again - is there any progress regarding this?

Thanks for pointing this out ... I also chimed in at #516.

As the author of #488, I'm inquiring as to whether there's any progress on this front. @hadley's last comment reflects exactly my use case ...

What's the status of this? Really looking forward to shallow clone support ...

Thank you for looking into this ... The problem persists and has now become even more pressing: as the `bioconductor` version has rolled over, the recent `bioconductor_docker:latest` (not just `bioconductor_docker:devel`)...

**BUT**: the CURRENT (as 0f 2021/06/02) `bioconductor_docker:devel` does NOT display the behavior in my hands, so it's now a remedy to move to that.

So from Fedora 35 to 36 there apparently was a major `podman` version switch with implied networking backend changes that were not backward compatible... but I can't find anything for...

That image gives me exactly the fame trouble as does the docker. Io one... On March 8, 2023 6:36:38 PM UTC, Alexandru Mahmoud ***@***.***> wrote: >Could you give ghcr.io/bioconductor/bioconductor:RELEASE_3_16 a...

As I wrote above: using the `docker.io/rocker/rstudio` image (which the `bioconductor` one uses as a base) works fine ... the port remapping issue should hit both ...

The issue persists as of 2023/03/31, BUT `docker.io/bioconductor/bioconductor_docker:devel` actually works!?