containers / podman-desktop-extension-ai-lab

We are currently using a pulling update mechanism to get the health check.

podman-desktop-extension-ai-lab/packages/backend/src/managers/inference/inferenceManager.ts

Line 280 in 529bc5b

    
           const intervalId = setInterval(this.updateServerStatus.bind(this, engineId, containerId), 10000);

We should move away from this behavior as it makes our extension use more resources when we already have access to this information through the podman desktop api events:

We already have some code able to capture container events.

podman-desktop-extension-ai-lab/packages/backend/src/managers/inference/inferenceManager.ts

Lines 290 to 293 in 529bc5b

    
           case 'die': 
        
             this.updateServerStatus(engineId, containerId); 
        
             clearInterval(intervalId); 
        
             break;

The migration would be relatively easy and simplify the code for InferenceManager.

In the new Podman 5.1.0 version, they introduced a new healthcheck_events allowing to remove the health events.

A new field, healthcheck_events, has been added to containers.conf under the [engine] section to allow users to disable the generation of health_status events to avoid spamming logs on systems with many healthchecks.¹

When we will start using those events, we would have to check that the config does not have this, otherwise healthcheck could not be verified.

https://github.com/containers/podman/releases/tag/v5.1.0 ↩

	case 'die':
	this.updateServerStatus(engineId, containerId);
	clearInterval(intervalId);
	break;

Stop using pulling update for Inference server health

Footnotes