scicco

> @scicco how does the above work for you without any sudo? It simply does not work for me without sudo - if you add fakeroot, fakeroot isn't allowed to...

I think #61 will address only the use case of a `singularity-compose.yml` config file containing `network.args`. If the config doesn't use it it still fails. It should be useful to...

it should match the [name](https://github.com/singularityhub/singularity-compose-examples/blob/master/v2.0/custom-network/50_static.conflist#L3) property of the cni configuration file, so in this case would be `static-redis`. I've updated the previous comment, I wrongly used `static` instead of `static-redis`

I've added a PR (#62) to try to address the --network "custom" type

That IP is probably leased by cni configuration when unchanged, so in this case: /usr/local/etc/singularity/network/00_bridge.conflist if you are using bridge (no fakeroot) or /usr/local/etc/singularity/network/40_fakeroot.configlist are specifying `plugins.ipam.subnet` property, which probably...

Ok, sure. Can you run singularity-compose without fakeroot options and use root? I'll modify my example repo to reproduce it

I've run your codebase version: https://github.com/singularityhub/singularity-compose/tree/e301c950c177ca6201769cce8d85243ce9158879 as root user: ``` $> singularity-compose up -d Creating redis1 singularity run instance://redis1 $> singularity instance list INSTANCE NAME PID IP IMAGE redis1 3063...

I've updated #62, adding a link to example repo with updated files for custom network

@vsoch can you try with this changes? 1. Ensure to have 10.22.0.0/16 inside /usr/local/etc/network/00_bridge.conflist `cat /usr/local/etc/network/00_bridge.conflist` ```yaml { "cniVersion": "0.4.0", "name": "bridge", "plugins": [ { "type": "bridge", "bridge": "sbr0", "isGateway":...

@vsoch sure. I've fixed and renamed the custom configuration because it was wrong (it used the same bridge name sbr0 which caused problems and switched into bridge cni config typology)....