-
Notifications
You must be signed in to change notification settings - Fork 126
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
panic: runtime error: invalid memory address or nil pointer dereference #208
Comments
+1 we're affected by this issue tooo:
|
@nixelsolutions Did you solve this problem? |
These are two different issues. Can you post your Docker version?
…On Dec 4, 2016 9:03 PM, "yeruisen" ***@***.***> wrote:
@nixelsolutions <https://github.com/nixelsolutions> Did you solve this
problem?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#208 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAP6Ir5GkmTF1IxL5T400zGbOzHGn39xks5rE3EHgaJpZM4KuYsj>
.
|
@yeruisen nope, still suffering it. @ehazlett this is the docker info output on swarm cluster:
The swarm nodes are running docker 1.10.2 though. |
I made a significant update to the docker client dependency as well as some other fixes. Can you try the latest |
Saw this happen in 1.3.2 but 1.4 appears to have resolved. |
test/integration: Ignore extra docker service create output
docker info
docker-compose.yml
config.toml
In my Swarm cluster, When I run docker-compose up to start my app, interlock throw execption.
The text was updated successfully, but these errors were encountered: