Skip to content

Spaces in path to openverse repository causing issues with ov #4636

Open

Description

Description

I was recently working with a potential contributor to get them set up with the project using ov. They were on MacOS, and we ran into some really odd issues that took some time to troubleshoot. Most of them came down to the fact that we had cloned the repository into a folder path which had a space in it. This caused an issue with this line in the docs (which will just require quoting the path to ov):

ln -s $(git rev-parse --show-toplevel)/ov ~/.local/bin/ov

The other issue we ran into was really odd, I didn't have much opportunity to debug the exact cause, but here was the error message:

$ ./ov just build

OCI runtime exec failed: exec failed: unable to start container process: chdir to cwd ("/Users/<username>/Openverse Projects/openverse") set in config.json failed: no such file or directory: unknown

Can someone with MacOS try the following steps to reproduce? I think we should either 1) try to make our documentation/commands robust to spaces or 2) add a warning not to have spaces in the path for where the Openverse repo will be cloned.

Reproduction

  1. Run ov stop && ov clean
  2. Clone the repository into a location with a space
  3. Run ./ov build in that directory (to create a new image)
  4. Run ./ov just build and attempt to see if you run into the above error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    • Status

      📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions