General info on the topic of running an SSH key agent can be found at the link below, note that Vagrant-DSpace is configured to use a key agent if one is running.
https://www.phase2technology.com/blog/running-an-ssh-agent-with-vagrant/ --Hardy On Fri, Nov 18, 2016 at 3:48 PM, Hardy Pottinger <[email protected]> wrote: > I know this will bring small comfort, but I've rechecked the two machines > I do most of my DSpace development on (OSX and Ubuntu), and on both of them > a full vagrant destroy -f cycle (with vagrant box remove added to the mix) > still ends up with a working Vagrant-DSpace. > > I'm wondering if perhaps you don't have an SSH key agent set up on your > host machine? > > > vagrant-ssh then ssh -T -oStrictHostKeyChecking=no [email protected] gives > > Permission denied (publickey). > > with an exit status of, as it says in the error message, 255. > > What OS is your host running? > > --Hardy > > On Fri, Nov 18, 2016 at 1:55 PM, Andrew Parker <[email protected]> > wrote: > >> I ran vagrant up after deleting the box image and running vagrant >> destroy -f, but I still got the previously referred to errors. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "DSpace Technical Support" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
