Choosing k8s-file logging net]# podman psĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS net]# podman ps -allĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESĢ6cbabe911eb docker.io/haugene/transmission-openvpn:latest dumb-init /etc/op. Create /etc/containers/nodocker to quiet msg.ĮRRO json-file logging specified but not supported. Storing net]# docker run -cap-add=NET_ADMIN -d \Įmulate Docker CLI using podman. Trying to pull docker.io/haugene/transmission-openvpn:latest. Resolved "haugene/transmission-openvpn" as an alias (/var/cache/containers/nf) Any ideas of where I might look to get some clue on the data]# docker pull haugene/transmission-openvpn I know for certain it's not a login issue, and I'm using the exact same syntax I used previously. I'm not sure where else to look to figure out what might be causing it to not start.
I had no problems with it working on Rocky 8, but now it consistently fails to start. I keep trying to rebuild my "haugene/transmission-openvpn" docker image.
I've been running my home server on Rocky 8.x since it came out, and just rebuild it using Rocky 9.0.
0 kommentar(er)
