Mount the user's SSH config file to Support 1Password SSH agent and possibly other agents

[nckrtl]

It would be nice if the user's ssh config would be mounted as well by default when running the provision command. And perhaps pass it by default. Typically the ssh config file is located at ~/.ssh/config.

Currently you can only pass a config file by copying the ssh config file manually, add it to the root of the project and run spin provision -u root --ssh-extra-args='-F config'

By mounting/passing the ssh config file support can be added for custom ssh agents which can be configured through the ssh config file, like 1Password's ssh agent.

[jaydrogers]

Thanks! I will take a look into this and will keep you posted 👍

[jaydrogers]

I finally had a chance to take a look into this. I am mounting the entire .ssh folder here:

spin/lib/functions.sh

Lines 701 to 708 in 62c26d4

	--allow-ssh)
	additional_docker_args+=("-v" "$HOME/.ssh/:/root/.ssh/" "-v" "$ansible_collections_path:/root/.ansible/collections")
	# Mount the SSH Agent for macOS systems
	if [[ "$(uname -s)" == "Darwin" ]]; then
	additional_docker_args+=("-v" "/run/host-services/ssh-auth.sock:/run/host-services/ssh-auth.sock" "-e" "SSH_AUTH_SOCK=/run/host-services/ssh-auth.sock")
	fi
	shift
	;;

I'm assuming this should include the .ssh/config file automatically.

Is it something with Linux not being able to interpret the 1password integration?

We're running Ansible & SSH from within the Ansible container (not macOS)

[nckrtl]

I'm getting ansible errors with 2.2.0 when deploying/provisioning as described here #115. Should work out of the box right?

[nckrtl]

Still same behaviour, but now my workaround is also no longer working. But ssh-extra-args='-F ' seems to actually look for the file specified, as it must be a valid path else I get an error the config isn't found. Before this was not the case.

I'm not surprised the workaround no longer works btw as it felt pretty hacky that is was working anyways. I will need to figure out the proper way to communicate with 1Password I guess.

[nckrtl]

After some more digging it turns that RUN_AS_USER is causing issues for me in run_ansible() in functions.sh when provisioning

When I change it from

  docker run --rm -it \
    -e "PUID=${SPIN_USER_ID}" \
    -e "PGID=${SPIN_GROUP_ID}" \
    -e "RUN_AS_USER=$(whoami)" \
    "${additional_docker_args[@]}" \
    "$SPIN_ANSIBLE_IMAGE" \
    "${args_without_options[@]}"

to: (also removed PUID and GUID as it caused issues as well described here: #115 (comment))

 docker run --rm -it \
   "${additional_docker_args[@]}" \
   "$SPIN_ANSIBLE_IMAGE" \
   "${args_without_options[@]}"

It actually does forward the ssh connection to 1password

[jaydrogers]

Working on a solution. I think I have it fixed, I just have to push a release. Stay tuned 😃

[jaydrogers]

This might fix it 🤞

#115 (comment)

[nckrtl]

Jay got it resolved, check out the solution here: https://serversideup.net/how-to-get-ssh-to-work-with-1password-docker-desktop-macos-within-a-container/