Johannes Gerold
Johannes Gerold
The user part of my issue is probably related to lspcontainers/dockerfiles#65.
I found the problem for the network bridge. Rootless Podman containers do not have access to the host network bridge, that's why there are errors when trying to pass `--network=bridge`...
Another option would be to check the container runtime and either use bridge or slirp4netns depending on that.
I want to work on this, you can assign it to me if you want.
Should the networking mode be also contained as an setup variable? When we then create the docker/podman command the `network` parameter could just be a boolean to switch between `none`...
Would it be a good idea to maybe add named volumes as default values for this? I am doing this with my own setup at the moment. This enables persisting...
> I've been using `bubblewrap` to sandbox some locally-installed containers, and I'm defining per-LSP config with this format: > > ```lua > network = true, > volumes = { >...
Okay I'm sorry I was wrong then. How would a named volume setup look with the table style configuration? lua ``` network = true, volumes = { { host =...
Would allowing functions as parameters for the extra volumes make sense? I just thought of that because functions would then enable something like this: ```lua image = "docker.io/lspcontainers/gopls", extra_volumes =...
I will test it later today or in the next few days, thanks!