[ 
https://issues.apache.org/jira/browse/GUACAMOLE-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Jelonek updated GUACAMOLE-2035:
-----------------------------------------
    Description: 
The guacd docker container contains a healthcheck that runs in a 5 minute 
intervall. It is lacking the start-up period parameter which would make sure 
that the check is only run after a set amount of time after start upm of the 
container.

This leads to problems with docker compose stacks that use the condition 
"service_healthy" in conjunction with the depends_on parameter to make sure 
that the guacd service is up and running before starting the guacamole web ui 
service. If the first run is missed the check is only performed again after 5 
minutes which effectively prevents the dependent service from spinning up as 
the guacd container is stuck in "starting" state for at least 5 minutes.

To fix that issue the start-up period parameter should be added with a 
reasonable value to ensure an immediate healthn check after spinning up of the 
guacd container.

 

Created an according PR here: [GUACAMOLE-2035: Add start-up period to guacd 
health check in Dockerfile by jeloneal · Pull Request #577 · 
apache/guacamole-server|https://github.com/apache/guacamole-server/pull/577]

  was:
The guacd docker container contains a healthcheck that runs in a 5 minute 
intervall. It is lacking the start-up period parameter which would make sure 
that the check is only run after a set amount of time after start upm of the 
container.

This leads to problems with docker compose stacks that use the condition 
"service_healthy" in conjunction with the depends_on parameter to make sure 
that the guacd service is up and running before starting the guacamole web ui 
service. If the first run is missed the check is only performed again after 5 
minutes which effectively prevents the dependent service from spinning up as 
the guacd container is stuck in "starting" state for at least 5 minutes.

To fix that issue the start-up period parameter should be added with a 
reasonable value to ensure an immediate healthn check after spinning up of the 
guacd container.


> Add start-up period to guacd health check in Dockerfile
> -------------------------------------------------------
>
>                 Key: GUACAMOLE-2035
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-2035
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacd-docker
>    Affects Versions: 1.5.5
>            Reporter: Alexander Jelonek
>            Priority: Minor
>
> The guacd docker container contains a healthcheck that runs in a 5 minute 
> intervall. It is lacking the start-up period parameter which would make sure 
> that the check is only run after a set amount of time after start upm of the 
> container.
> This leads to problems with docker compose stacks that use the condition 
> "service_healthy" in conjunction with the depends_on parameter to make sure 
> that the guacd service is up and running before starting the guacamole web ui 
> service. If the first run is missed the check is only performed again after 5 
> minutes which effectively prevents the dependent service from spinning up as 
> the guacd container is stuck in "starting" state for at least 5 minutes.
> To fix that issue the start-up period parameter should be added with a 
> reasonable value to ensure an immediate healthn check after spinning up of 
> the guacd container.
>  
> Created an according PR here: [GUACAMOLE-2035: Add start-up period to guacd 
> health check in Dockerfile by jeloneal · Pull Request #577 · 
> apache/guacamole-server|https://github.com/apache/guacamole-server/pull/577]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to