Closed Altai-man closed 4 years ago
zef will reside in the standard location, /home/whatever/.zef. I don't think you're mounting it from outside. The image will be persistent unless you tell it otherwise running it with --rm
Who can I ping to update the Blin image? Namely, got goodies from enchance branch just merged and look into zef version used or taking care of .zef cache so that it doesn't prevent HTTP::UserAgent installations (dozens of modules depend on that).
I haven't looked at it so far, but I don't think that's the issue.
I'll try and check the image, if that's the problem.
So I built a container based on https://github.com/nxadm/raku-blin-docker locally and it works, so closing. Thanks to @stoned who suggested the overall idea of resolving it in such a fashion.
I'd resolve it myself, but sadly don't know enough about the infrastructure, so hoping anyone can provide some info about this situation.
Let's look at this output:
I know the solution is to
zef nuke StoreDir
or justrm .zef
with old cache. But.How do one does that with docker setup? In our docker setup, where does
.zef
resides? Is it persistent between container runs? Usingpodman ps -a
I see there are dozens of containers who already exited onlatest
...Who can I ping to update the Blin image? Namely, got goodies from
enchance
branch just merged and look into zef version used or taking care of .zef cache so that it doesn't preventHTTP::UserAgent
installations (dozens of modules depend on that).