Aspirate apply doesn't take BindMount custom configurations

[PedemonteGiacomo]

🔥 Bug Description

I need to find a solution to this problem, where I want to pass custom configuration to container I done that with BindMount and with docker env. and dotnet run, locally, works.

But when I use aspirate I get that the configuration is not taken and no logs are printed that the bind mount were ignored or something else... it just don't apply them so my container deployments doen't have the volume mount with the respective configurations.

An example as code:

var envoy = builder.AddContainer("envoyproxy", "envoyproxy/envoy",tag:"v1.29-latest")
                   .WithBindMount("../envoy/envoy.yaml", "/etc/envoy/envoy.yaml")
                   .WithEndpoint(port: 80, targetPort: 10000, name: "envoy-port", scheme: "http");

The BindMount is properly reported to the manifest as I report here

{
  "resources": {
    "envoyproxy": {
      "type": "container.v0",
      "image": "envoyproxy/envoy:v1.29-latest",
      "bindMounts": [
        {
          "source": "../envoy/envoy.yaml",
          "target": "/etc/envoy/envoy.yaml",
          "readOnly": false
        }
      ],
      "bindings": {
        "envoy-port": {
          "scheme": "http",
          "protocol": "tcp",
          "transport": "http",
          "port": 80,
          "targetPort": 10000
        }
      }
    },

But when I apply the manifest the bindmount is "skipped" and I don't obtain my services working as I need.

Does anyone have the same issue? What's the problem in this?