Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installer: Handle non-writable /usr/local #1660

Closed
ndarilek opened this issue Mar 18, 2016 · 2 comments
Closed

Installer: Handle non-writable /usr/local #1660

ndarilek opened this issue Mar 18, 2016 · 2 comments

Comments

@ndarilek
Copy link
Contributor

@ndarilek ndarilek commented Mar 18, 2016

Trying to come up with the ultimate, hands-off, don't-have-to-touch-it Sandstorm installation for organizations with no or little tech competency. I think CoreOS and its automatic security updates might make a great choice since both the OS and Sandstorm could upgrade themselves without interaction.

Only, unfortunately /usr/local/bin isn't writable under CoreOS--or, at least, the installer fails trying to write the /usr/local/bin symlink. Would it be possible for the installer to either a) skip creating the /usr/local/bin symlink if writing fails, or b) put it in /opt/sandstorm/bin? I don't know if the systemd unit file accesses the binary directly, but I'm pretty sure /etc/systemd/system is writable so that much should work, and the unit could be updated to always access it directly rather than via the symlink.

Thanks.

@paulproteus
Copy link
Collaborator

@paulproteus paulproteus commented Mar 22, 2016

@ndarilek
Copy link
Contributor Author

@ndarilek ndarilek commented Mar 22, 2016

  1. Yes, it is read-only. I think everything outside of /opt and /etc is
    mounted RO.
  2. CoreOS has /opt/bin in the user's $PATH by default, though in my
    fresh VM /opt doesn't exist. It can be created just fine though.

CoreOS is indeed 100% systemd.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.