This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
DuplicateKeyError provides no indication of the problematic YAML #1803
Labels
Comments
I was on 1.9.0, I upgrated to 1.10.1 and still have the issue on restart.
|
Though the error indicates a duplicate key (and the attribute), there is no other indication of where to look for the problem. |
jrryjcksn
changed the title
DuplicateKeyError
DuplicateKeyError provides no indication of the problematic YAML
Mar 7, 2019
I was able to log in to the container, move
By doing that I was able to find my yaml error which was a copy/paste error. This showed me the file that had the problem:
It still would be nice to have the filename given when |
Absolutely -- sorry you had to hack the container to get that info. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This seemed to prevent a pod from updating when a new version appeared on docker. It had worked many times before.
Here is a longer section of the logs for reference:
The text was updated successfully, but these errors were encountered: