You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using docker ( alias rekcod='docker run --name rekcod --rm -i -v /var/run/docker.sock:/var/run/docker.sock nexdrew/rekcod' ) on a container created by Portainer (likely not relevant?) it fails to recover specified IP addresses.
Obviously I've pruned the output here for privacy as much as I can be bothered, but I didn't remove any parameters (except volumes) and merely censored/changed network topology information.
(While it's on my mind - is there a way we can "pretty-print" that with newlines via argument to rekcod? That would make life easier. I tried to run it with no parameters to check options and had to kill the docker PID to get my ssh terminal back. YIKES.)
There's clearly a lot of junk there created by the container and/or Portainer, but the relevant section of the Stack (Portainer's docker-compose wrapper thing) is such;
Importantly - the networks/<network_name>/ipv4_address tag is not being caught. Sorry for so much extra information, didn't want to overly prune it and invalidate the issue.
The text was updated successfully, but these errors were encountered:
Using docker ( alias rekcod='docker run --name rekcod --rm -i -v /var/run/docker.sock:/var/run/docker.sock nexdrew/rekcod' ) on a container created by Portainer (likely not relevant?) it fails to recover specified IP addresses.
Obviously I've pruned the output here for privacy as much as I can be bothered, but I didn't remove any parameters (except volumes) and merely censored/changed network topology information.
(While it's on my mind - is there a way we can "pretty-print" that with newlines via argument to rekcod? That would make life easier. I tried to run it with no parameters to check options and had to kill the
docker
PID to get my ssh terminal back. YIKES.)There's clearly a lot of junk there created by the container and/or Portainer, but the relevant section of the Stack (Portainer's docker-compose wrapper thing) is such;
Importantly - the networks/<network_name>/ipv4_address tag is not being caught. Sorry for so much extra information, didn't want to overly prune it and invalidate the issue.
The text was updated successfully, but these errors were encountered: