GeorgeS2019 commented on issue #81:
URL: 
https://github.com/apache/openwhisk-runtime-dotnet/issues/81#issuecomment-2403843840

   ### [WIP] Using Podman for deploying OpenWhisk and using 
OpenWhisk-runtime-Dotnet
   
   
   To modify the OpenWhisk configuration to use Podman instead of Docker, 
you'll need to adjust the container runtime settings. Here are the detailed 
steps:
   
   1. **Install Podman**:
      - Ensure Podman is installed on your system. You can follow the 
installation instructions on the [Podman 
website](https://podman.io/getting-started/installation).
   
   2. **Update OpenWhisk Configuration**:
      - OpenWhisk uses a configuration file to manage its settings. You will 
need to modify this file to specify Podman as the container runtime.
      - Locate the `application.conf` file in your OpenWhisk deployment. This 
file is typically found in the `whisk` directory.
      - Update the container factory settings to use Podman. For example:
        ```hocon
        whisk {
          containerFactory {
            impl = "whisk.core.containerpool.docker.DockerContainerFactory"
            docker {
              runCmd = "podman run"
              inspectCmd = "podman inspect"
              rmCmd = "podman rm"
              psCmd = "podman ps"
            }
          }
        }
        ```
   
   3. **Restart OpenWhisk**:
      - After updating the configuration, restart your OpenWhisk services to 
apply the changes. This can typically be done using the deployment scripts or 
commands specific to your setup.
   
   4. **Verify the Configuration**:
      - Ensure that OpenWhisk is now using Podman by checking the logs and 
running a few test actions. You can use the OpenWhisk CLI to invoke actions and 
verify that they are being managed by Podman.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to