Skip to content

When running in the home directory on MacOS - ocm-container fails to start. #481

@iamkirkbater

Description

@iamkirkbater

When running directly on the home directory ~ on MacOS (unconfirmed on Linux, most likely not an issue) the container will fail to start with seemingly random error messages, but all of them share the same pattern:

Error: statfs /var/home/core/.config/gcloud: no such file or directory
Error: statfs /var/home/core/.config/ocm-container/per-cluster-persistent/REDACTED: no such file or directory
Error: statfs /var/home/core/.config/backplane/config.yaml: no such file or directory

Judging by the filesystem that is being stat - I assume this means that when running in the home directory directly it's then checking for the presence of the config files in the podman-machine's HOME directory, and not in the mounted /Users/user/ directory.

However, when I go into a sub-folder of my home directory, it works just fine.

$HOME is set while I'm in my home directory, so additional debugging is necessary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions