Skip to content

config file source/container-engine mixup #353

Open
@EdJoPaTo

Description

@EdJoPaTo

When using source: podman it seems to work. When using container-engine: podman like its stated within the readme it does not.

From never programming go before I assume viper is doing the config/cli arguments. Both viper.GetString("source") and viper.GetString("container-engine") are used within the project but I havnt figured out much about the project so far and only had a short look.

Is the container-engine: podman config entry in the readme simply outdated? Was this forgotten after #283? What confuses me about it: #267 states the other way around. Was this option possible the other way around before?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    • Status

      Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions