Closed minusdelta closed 4 years ago
According to the docs pipework should be able to resolve Docker container names. This seems to be broken:
CONTAINER=bagpipe docker run --rm -d --name $CONTAINER -it alpine sh pipework dummy -i lo123 $CONTAINER 10.1.2.3/32
head: cannot open '/tasks' for reading: No such file or directory
ID=$(docker inspect $CONTAINER |jq -r .[].Id) pipework dummy -i lo123 $ID 10.1.2.3/32 docker exec $CONTAINER ip -o a s dev lo123
43: lo123 inet 10.1.2.3/32 scope global lo123
Sorry, just ignore me ... just seconds after opening this I saw that there was a commit recently that fixes this. I am not used to see commits here :-)
According to the docs pipework should be able to resolve Docker container names. This seems to be broken: