Skip to content

Fixed the DockerRuntime to apply the provided HostConfig, thereby supporting volume mount functionality #522

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

Merged
merged 1 commit into from
Jul 22, 2025

Conversation

cdavernas
Copy link
Member

Many thanks for submitting your Pull Request ❤️!

What this PR does / why we need it:

  • Fixes the DockerRuntime to apply the provided HostConfig, thereby supporting volume mount functionality
  • Fixes the DockerContainerPlatform to properly initialize containers binds, thereby supporting volume mount functionality
  • Fixes the docker-compose deployment by replacing Garnet by Redis

Fixes #521

…fig`, thereby supporting volume mount functionality

fix(Docker): Fixed the `DockerContainerPlatform` to properly initialize containers binds, thereby supporting volume mount functionality
fix(DockerCompose): Fixed the docker-compose deployment by replacing `Garnet` by `Redis`

Signed-off-by: Charles d'Avernas <charles.davernas@neuroglia.io>
@cdavernas cdavernas requested a review from Copilot July 22, 2025 19:51
@cdavernas cdavernas self-assigned this Jul 22, 2025
@cdavernas cdavernas added type: enhancement New feature or request priority: high Indicates a high priority issue weight: 2 An issue with a low development impact app: operator Concerns the Operator labels Jul 22, 2025
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR fixes Docker runtime functionality to properly support volume mounting and updates deployment configuration to use Redis instead of Garnet. The changes also include spelling corrections for "preferred" vs "prefered" throughout the dashboard components.

  • Enables volume mount functionality by properly applying provided HostConfig in DockerRuntime
  • Fixes container volume binding syntax in DockerContainerPlatform
  • Replaces Garnet with Redis in docker-compose deployment configuration

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
src/runtime/Synapse.Runtime.Docker/Services/DockerRuntime.cs Updated to use provided HostConfig and insert mounts at specific positions
src/dashboard/Synapse.Dashboard/wwwroot/index.html Fixed spelling from "prefered" to "preferred"
src/dashboard/Synapse.Dashboard/Services/JsInterop.cs Fixed spelling from "prefered" to "preferred"
src/dashboard/Synapse.Dashboard/Layout/MainLayout.razor Fixed spelling from "prefered" to "preferred"
src/core/Synapse.Core/Resources/DockerRuntimeConfiguration.cs Added HostConfig property and updated property ordering
src/core/Synapse.Core.Infrastructure.Containers.Docker/DockerContainerPlatform.cs Fixed volume binding syntax from "=" to ":"
deployments/docker-compose/docker-compose.yml Replaced Garnet with Redis service
deployments/docker-compose/.env Updated connection string from Garnet to Redis

@cdavernas cdavernas merged commit a1bc5c4 into main Jul 22, 2025
2 checks passed
@cdavernas cdavernas deleted the fix-volume-mounts branch July 22, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app: operator Concerns the Operator priority: high Indicates a high priority issue type: enhancement New feature or request weight: 2 An issue with a low development impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Runner container volume mounts can't be configured due to missing HostConfig
1 participant
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy