Unable to install on Ubuntu 16.10

[jochenparm]

Hi, when running the installation commands you provide, I get the following error message:

docker run --interactive --tty --rm --volume "/usr/local/bin:/silo_install_path" grpn/ansible-silo:2.1.0 --install
Installing from ansible-silo 2.1.0:

• ansible will be created
  cp: can't create symlink '/silo_install_path/ansible': Read-only file system
• ansible-config will be created
  cp: can't create symlink '/silo_install_path/ansible-config': Read-only file system
• ansible-console will be created
  cp: can't create symlink '/silo_install_path/ansible-console': Read-only file system
• ansible-doc will be created
  cp: can't create symlink '/silo_install_path/ansible-doc': Read-only file system
• ansible-galaxy will be created
  cp: can't create symlink '/silo_install_path/ansible-galaxy': Read-only file system
• ansible-lint will be created
  cp: can't create symlink '/silo_install_path/ansible-lint': Read-only file system
• ansible-playbook will be created
  cp: can't create symlink '/silo_install_path/ansible-playbook': Read-only file system
• ansible-pull will be created
  cp: can't create symlink '/silo_install_path/ansible-pull': Read-only file system
• ansible-silo will be created
  /silo/silo_functions.sh: line 447: /silo_install_path/ansible-silo: Read-only file system
  chmod: /silo_install_path/ansible-silo: No such file or directory
• ansible-vault will be created
  cp: can't create symlink '/silo_install_path/ansible-vault': Read-only file system
  Done

Do you have an idea what I'm missing? Is the problem my read/write access to "/usr/local/bin:/silo_install_path" ?

[udondan]

Sorry @jochenparm for the delay. Yes it probably is due to write permissions to /usr/local/bin.

You should be able to do it like that:

docker run --interactive --tty --rm --volume "/tmp/bin:/silo_install_path" grpn/ansible-silo:2.1.0 --install
sudo mv /tmp/bin/* /usr/local/bin

Let me know if that works for you or not.

This should probably be mentioned in the docs.

[espoelstra]

+1 for not abusing --privileged and leaving it to the user to have sudo rights to perform the move. That would allow prompting from mv in the future if the file existed already and the user was going to overwrite it.