Joshua Hogendorn
Joshua Hogendorn
I'm experiencing this also on 11.4
Quick update, you can move past this by: ``` pip install certifi CERT_PATH=$(python -m certifi) export SSL_CERT_FILE=${CERT_PATH} export REQUESTS_CA_BUNDLE=${CERT_PATH} ```
Is this considered fixed or still outstanding? I'm experiencing this issue with the jekyll/jekyll container, on the HEAD install of colima, lima, qemu. I've tried following these instructions: https://github.com/lima-vm/lima/issues/231#issuecomment-1145113879 But...
> @jhogendorn what is your exact situation? Have you tried starting Colima with `--mount-type 9p`? I'm running a jekyll container with docker compose. ``` version: '2.2' services: jekyll: image: jekyll/jekyll:stable...
> Does it work if you specify the `uid` manually by adding `user: 501` to your docker compose file? You can verify your uid in the terminal with `id -u`....
I will note its managed to create a directory structure inside .jekyll-cache, and has some files inside that. Perhaps this is limited to the 'top level' of the mount? It...
chmod 777 does work. thats a rough hack though. I ended up swapping to a different base container, it became evident the issues were many and mostly around that particular...
I'd really like to see this happen as well. Happy to do a PR or whatever is appropriate to help.
I have been experiencing this for ages also, hoping it was obvious and would be fixed but evidently not. has anyone got insights on to whats going on here?
Quick extra note, if you trust your readers, `HTTPS://` can be swapped for `WWW.`, gives 4 extra chars of namespace.