Missing agent.sock: 1Password on Arch Linux (AUR) Prevents CLI Desktop Integration

1Password CLI in Distrobox Container Can't Connect to Host App

On CachyOS (an Arch-based distribution), the native 1Password desktop application installed from the AUR does not create the necessary agent.sock file and its containing directory for CLI integration. While the CLI on the host machine works, this missing socket makes it impossible to connect the CLI from inside a Distrobox (Ubuntu) container to the host's 1Password application.

Steps to Reproduce:

1. Install CachyOS.
2. Install the 1password package via the recommended AUR method.
3. Launch the 1Password desktop app, unlock it, and enable "Integrate with 1Password CLI" in the Developer settings.
4. Install distrobox and podman.
5. Attempt to create a new Ubuntu container with the 1Password socket directory mounted:

distrobox create -n my-container -i ubuntu:22.04 --volume "$XDG_RUNTIME_DIR/1Password:$XDG_RUNTIME_DIR/1Password"

Expected Behavior: The 1Password host application should create the socket directory at $XDG_RUNTIME_DIR/1Password containing agent.sock. The distrobox create command should succeed, and the op CLI inside the container should then be able to communicate with the host's 1Password app.

Actual Behavior: The host application fails to create the socket directory. Checking for it results in an error: 

ls: cannot access '/run/user/1000/1Password': No such file or directory

Consequently, the distrobox create command fails with the error:

statfs /run/user/1000/1Password: no such file or directory.

The CLI inside the container cannot be used with desktop app integration.

System Details:

• Operating System: CachyOS (Arch-based)
• 1Password Version: 2.31.1
• Installation Method: AUR
• CLI Version: 2.31.1
• Container Image: Ubuntu (via Distrobox)

Troubleshooting Steps Taken:

• Confirmed CLI integration is enabled in the app settings.
• Confirmed the CLI works correctly on the host machine itself.
• Performed a full system update and rebooted.
• Confirmed via pacman -Qi 1password that this is a native package, not a Flatpak or Snap.
• Searched the entire filesystem for agent.sock using the find command, and no relevant socket file was found.