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
I've got a bit of a circular dependency going at the moment, where container A needs to know the IP of container B, and vice-versa, but their environment variables and host files can become out of sync when one or the other is re-started. It would be nice to predictably determine their IPs, perhaps by giving them a pre-determined mac address and then using IPv6. I think we could track a similar effort to support these additional run options as at docker/compose#754
Along with #129 and #130, just documenting a few things that I've run into in my own use of maestro this week as I transition to a container-based workflow. Basically just documenting a few things that would be nice to have, and I think I might even be able to knock a few of them out since this is based on docker-py.
The text was updated successfully, but these errors were encountered:
I've got a bit of a circular dependency going at the moment, where container A needs to know the IP of container B, and vice-versa, but their environment variables and host files can become out of sync when one or the other is re-started. It would be nice to predictably determine their IPs, perhaps by giving them a pre-determined mac address and then using IPv6. I think we could track a similar effort to support these additional run options as at docker/compose#754
Along with #129 and #130, just documenting a few things that I've run into in my own use of maestro this week as I transition to a container-based workflow. Basically just documenting a few things that would be nice to have, and I think I might even be able to knock a few of them out since this is based on docker-py.
The text was updated successfully, but these errors were encountered: