Joffrey F
Joffrey F
This should work, unless I'm misunderstanding the use case. ``` version: "2" networks: bar.com: services: foo: networks: bar.com: aliases: - foo.bar.com ```
The error message should be improved in the next release. As for actually supporting port ranges, the v3 format would need to be updated first - these changes happen at...
> It also does not support not stating which port published should be used. Actually, you can do that by not stating which port to publish, e.g. ```yaml version: '3.5'...
The original design was that because it was the high-level client, the result (image object or exception in case of failure) was more important to the user than the logs...
@hnine999 No, that's an error on our end - we'll fix it shortly. Feel free to submit your PR in the meantime!
Hi! Unfortunately, Machine is now in maintenance mode, meaning we're not merging new features anymore and sticking to bug fixes. Thank you for your understanding.
This is not temporary, but that doesn't mean the project is dead, simply that we are not looking to add any new features. See #4537 for details.
@gilbsgilbs You can still use docker-machine as you currently do!
@justinclift I don't want to get into too much detail because we've got more info coming in a prepared statement, but as I tried to state in the original post,...
http://docker-py.readthedocs.io/en/stable/images.html#docker.models.images.ImageCollection.push > **decode** (*bool*) – Decode the JSON data from the server into dicts. Only applies with `stream=True`