Add lan_address support in RPC and container management

- Introduced a new `lan_address` field in the RPC response for containers, allowing for easier access to UI launch URLs based on container names.
- Updated the `ContainerStatus` struct to include `lan_address`, ensuring it is initialized and passed through relevant methods in both Podman and Docker runtimes.
- Enhanced the UI store to compute enriched bundled apps with their respective `lan_address`, improving the user experience for accessing containerized applications.
- Modified the `ContainerApps` view to utilize the enriched data, ensuring the correct launch URLs are displayed for bundled apps.
This commit is contained in:
Dorian
2026-02-04 16:20:09 +00:00
parent 59072bd16c
commit d988396111
5 changed files with 41 additions and 6 deletions
+12
View File
@@ -96,6 +96,17 @@ export const useContainerStore = defineStore('container', () => {
return container.state
})
// Get enriched bundled apps with runtime data (like lan_address)
const enrichedBundledApps = computed(() => {
return BUNDLED_APPS.map(app => {
const container = getContainerForApp.value(app.id)
return {
...app,
lan_address: container?.lan_address
}
})
})
// Actions
async function fetchContainers() {
loading.value = true
@@ -240,6 +251,7 @@ export const useContainerStore = defineStore('container', () => {
getContainerForApp,
isAppLoading,
getAppState,
enrichedBundledApps,
// Actions
fetchContainers,
fetchHealthStatus,