-
Notifications
You must be signed in to change notification settings - Fork 2k
Support start_period for healthcheck in Docker Compose #475
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll also need to update cli/compose/convert/service.go to accept the new field.
I believe this will require an updated to the swarmkit dependency in vendor.conf, which will probably be blocked on #465
| }, | ||
| "timeout": {"type": "string"} | ||
| "timeout": {"type": "string"}, | ||
| "start_period": {"type": "string"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
indentation looks off. This file uses spaces not tabs.
cli/compose/types/types.go
Outdated
| Interval string | ||
| Retries *uint64 | ||
| StartPeriod string | ||
| StartPeriod string `mapstructure:"start_period"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This field should be a *time.Duration not a string. I just noticed that the other fields here are wrong. We'll need to fix that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
func convertHealthcheck(healthcheck *composetypes.HealthCheckConfig) (*container.HealthConfig, error)
will parse and convert the string into time.Duration
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will yes, but it's an unnecessary step. The config should be of type *time.Duration. This is a mistake that was made in other fields of the HealthCheckConfig (that we need to fix), but there are other fields in the service that use *time.Duration correctly.
Codecov Report
@@ Coverage Diff @@
## master #475 +/- ##
==========================================
- Coverage 48.62% 47.41% -1.21%
==========================================
Files 199 199
Lines 16396 16398 +2
==========================================
- Hits 7972 7775 -197
- Misses 8008 8228 +220
+ Partials 416 395 -21 |
68fb22c to
e94b6c7
Compare
e94b6c7 to
15d242e
Compare
Signed-off-by: Li Yi <denverdino@gmail.com>
099e73c to
0abdad6
Compare
|
Changed the type of interval, timeout and start_period of healthcheck from string to * time.Duration Thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, just one comment
| ] | ||
| }, | ||
| "timeout": {"type": "string"} | ||
| "timeout": {"type": "string", "format": "duration"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Normally we do not make any changes to previous versions of the schema. They should be frozen. Would you mind reverting this change in the previous versions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think the change on the datatype will impact the parsing for old version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, it wont
…from string to * time.Duration Signed-off-by: Li Yi <denverdino@gmail.com>
e19ef5c to
e02fcfd
Compare
|
@dnephin Thanks for your comments, the change on the 3.0~3.3 schema is reverted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🐮
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
I was waiting for this feature, but I think I am missing something here. start_period Additional property start_period is not allowed I checked the schema file in the 17.09 release of docker-ce and it seems correct. |
|
// edited: works with docker-compose file version 3.4 |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Signed-off-by: Li Yi denverdino@gmail.com
- What I did
The
--health-start-period durationis supported bydocker runanddocker service createsince 17.05, but it is missing in the Docker Compose.The PR adds the start_period for healthcheck to Docker Compose.
- How I did it
Adds the start_period for healthcheck to Docker Compose.
- How to verify it
Using the bellow compose file: docker-compose.yaml
docker stack deploy -c docker-compose.yaml elasticsearch
- Description for the changelog
Support start_period for healthcheck in Docker Compose
- A picture of a cute animal (not mandatory but encouraged)