Pipework: pipework commands not run when container is restarted

dreamcat4 / docker-images

Dreamcat4's Docker Images (Trusted Builds)

MIT License

159 stars 66 forks source link

Pipework: pipework commands not run when container is restarted #40

Closed schmurfy closed 4 years ago

schmurfy commented 6 years ago

I have a container with this environment:

pipework_cmd: eth0 -i eth1 @CONTAINER_NAME@ a.x.y.z/32

This works fine when the container is created but if the container is stopped and started again the ip is no longer associated with it.

schmurfy commented 6 years ago

I found more about this when switching debug mode, the problem is that I use a /32 which ends up running fping -c1 -t200 and after that the script is stuck.

micw commented 4 years ago

Got the same issue, how did you fixed this?

schmurfy commented 4 years ago

@micw I never fixed it, the project never got into production so I just gave up on this.