-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reflect.Value.Set using unaddressable value #972
Labels
Comments
@smur89 thx for the report. Can you provide a small set of compose-file that make the issue reproductible ? (to help me fixing it 😛 ) |
a small set of version: '3.3'
networks:
hostnet:
driver: overlay
ipam:
driver: default
config:
- subnet: 10.0.0.0/20
hostnet:
external:
name: 'host' This symptom has occurred right after installed the latest |
Sorry @vdemeester just seeing this now. Looks like you've got what you need from heycalmdown. Cheers |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BUG REPORT INFORMATION
Description
We recently split our docker-compose.yml file into multiple yaml files and upgraded to v18.03 to take advantage of the added native support for this as per https://github.com/docker/cli/pull/569/files
When deploying with the following command, we get an error and our stack fails to deploy.
Error:
The problem was related to having a network defined in our yaml files. When we removed this we didn't see this error any more.
Seems like a better error could be shown here
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Stack started
Additional information you deem important (e.g. issue happens only occasionally):
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
Running in AWS on CentOS
The text was updated successfully, but these errors were encountered: