# Install issues when not root **URL:** \ **Category:** Self-hosting\ **Created:** [June 14, 2014, 1:13pm UTC](https://meta.discourse.org/t/install-issues-when-not-root/16538 "2014-06-14T13:13:06Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![trident](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/trident/32/2078_2.png) [@trident](https://meta.discourse.org/u/trident)\ **Post date:** [June 14, 2014, 1:50pm UTC](https://meta.discourse.org/t/install-issues-when-not-root/16538/2 "2014-06-14T13:50:27Z")
> [@thornburg](#): > > 1. The install directions are no good. I had to cobble together answers from multiple sets of directions to get it working. ALSO, why in the world would I ever run a remote script without seeing its contents? This is the worst installation method ever. Only one part has you run scripts against your actual system. The [http://get.docker.io/](http://get.docker.io/) script handles a lot of the variables and performs some basic checks. You can always read it before running it, and you can always install those packages by hand. Every thing else runs inside a separate container that is isolated from the main system; the launcher script is simply copying the configuration file into environment variables and instructing docker to pull the correct images. > [@thornburg](#): > > 1. I eventually got Docker & Discourse running. Everything was fine, except I couldn’t SSH into the docker container. I’ve seen multiple statements that this is supposed to be “automatic” now. It’s not. How do I fix it? I’ve seen comments about copying a key somewhere, but no one says where I get the key (or even what key it is). I’ve had problems with this too… but I always thought it was something I was doing wrong. In fact, I just fired up a plain ubuntu vm and the key still did not copy correctly. I’ve got a vm packaged with the issue if needed. I took some time and thought about this. It looks like it works if you bootstrap while fully logged in as root; and not if you escalate via sudo. If you go the sudo route, it tries to create a key for the non-root user but never copies it over. > [@thornburg](#): > > 1. The upgrade doesn’t work. It looks to me like it’s trying to do operations that require admin privileges without using sudo. Normally I would just SSH and run the commands with sudo myself, but I can’t (see 3). What does not work exactly? Commands are being run against the docker container and not your actual system, so it does not require real or sudo root access. What step does it seem to hang on? --- _[View the full topic](https://meta.discourse.org/t/install-issues-when-not-root/16538)._