Public | Automated Build

Last pushed: 9 days ago
Short Description
Cloud9 instance
Full Description

#Cloud9 instance

Docker hub: https://registry.hub.docker.com/u/sapk/cloud9/

Usage

Start with auth

docker run -d -v $(pwd):/workspace -p 8181:8181 sapk/cloud9 --auth username:password

You can also use any starting option describe in : https://github.com/c9/core

Use custom user settings

docker run -d -v $(pwd):/workspace -v /home/user/c9.settings:/root/.c9/user.settings -p 8181:8181 sapk/cloud9

Where /home/user/c9.settings is the user.settings file on your file system

Notes

If you want to only expose cloud9 localy use -p 127.0.0.1:8181:8181 instead of -p 8181:8181. Otherwise it will be accesible to any equipement that can acces to your PC through the network.

You need to set auth because if not set the server will only listen to inner-container localhost host and woulndn't be available to the host.

Docker Pull Command
Owner
sapk
Source Repository

Comments (8)
techmuch
10 days ago

Is there a way to pass the auth using docker-compose.yml?

cloverzrg
3 months ago

@fferraro87: -p 80:8181

fferraro87
4 months ago

Hi, how can i use port 80 instead 8181?
Thanks

sapk
4 months ago

@torehc sorry for late response.
It use the same parms than c9/core so only one user if I believe https://github.com/c9/core/issues/241

torehc
8 months ago

Hello!
Does it support multiple users?

--auth username1:password1 --auth username2:password2

sapk
a year ago

@osobh Thanks to https://github.com/sapk/dockerfiles/pull/33 this problem should be fixed.

osobh
a year ago

today's build 08.02.2016 has some problems with pty.js missing which renders the terminal unusable. Is anyone else seeing this?

devnull42
a year ago

Just wanted to thank you for this build. I like that you included auth. I was having an issue with another cloud9 build where the browser preview wasn't functioning. Yours is working perfectly. Great work.