yep privileged made the network go

yep, privileged made the network go

7 Replies

bshermanOP•15mo ago

@akdev i think i've filled #💾ublue-dev with non ublue stuff enough... but i am super curious about this podman stuff now that you got me going i don't actually think i need privileged mode the cap_add: NET_ADMIN is enough

akdev•15mo ago

It does work?

bshermanOP•15mo ago

yes, it's kinda crazy and i have a justfile that's where the aux-address stuff was for the docker network create so i added this:

set dotenv-load
DOCKER := env_var_or_default('DOCKER_CMD', 'docker') 
setup:
    # Create network
    {{DOCKER}} network create qemukvm

set dotenv-load
DOCKER := env_var_or_default('DOCKER_CMD', 'docker') 
setup:
    # Create network
    {{DOCKER}} network create qemukvm

and if i have a .env file with DOCKER_CMD=podman it'll work for me... but for my debian developer... he gets to use docker... it's the simple things

akdev•15mo ago

Turns out podman on docker socket is not meant to work only docker on podman is meant to work

bshermanOP•15mo ago

yeah, this makes sense. podman team worked to ensure that their socket exposed a docker/docker-compose compatible api... but podman itself doesn't use the socket (except for some remote functions maybe?)

akdev•15mo ago

Yeah I was using podman —remote

bshermanOP•15mo ago

makes sense

Gaming

Programming

yep privileged made the network go