Public | Automated Build

Last pushed: 4 months ago
Short Description
Automated Cloud9 IDE (http://c9.io) Build
Full Description

Cloud9 v3 Dockerfile

This repository contains Dockerfile of Cloud9 IDE for Docker's automated build published to the public Docker Hub Registry.

Base Docker Image

kdelfour/supervisor-docker

Installation

Install Docker.

Download automated build from public Docker Hub Registry: docker pull kdelfour/cloud9-docker

(alternatively, you can build an image from Dockerfile: docker build -t="kdelfour/cloud9-docker" github.com/kdelfour/cloud9-docker)

Usage

docker run -it -d -p 80:80 kdelfour/cloud9-docker

You can add a workspace as a volume directory with the argument -v /your-path/workspace/:/workspace/ like this :

docker run -it -d -p 80:80 -v /your-path/workspace/:/workspace/ kdelfour/cloud9-docker

Build and run with custom config directory

Get the latest version from github

git clone https://github.com/kdelfour/cloud9-docker
cd cloud9-docker/

Build it

sudo docker build --force-rm=true --tag="$USER/cloud9-docker:latest" .

And run

sudo docker run -d -p 80:80 -v /your-path/workspace/:/workspace/ $USER/cloud9-docker:latest

Enjoy !!

Docker Pull Command
Owner
kdelfour
Source Repository

Comments (16)
raskan
4 months ago

hi!

how to add plugin?

srry: for my bad english

agartha
9 months ago

How can I run multiple instances of this docker container side-by-side with different port numbers? Specifying anything other than 80:80 does not seem to work...

kdelfour
2 years ago

@evilp Thank you, I'm going to integrate it in the container.

evilp
2 years ago

Here's a little tip to get SFTP Server mounts working:

start the container with the options --cap-add SYS_ADMIN --device /dev/fuse
e.g. docker run -it --cap-add SYS_ADMIN --device /dev/fuse -d -p 80:80 -v /your-path/workspace/:/workspace/ kdelfour/cloud9-docker

in container do:
apt-get update
apt-get install sshfs

now mount SFTP Server via the file menu works.

kdelfour
2 years ago

@kuaner : I have update the dockerfile, and now you can connect without auth if you want. I have also change the default port to 80.

kuaner
2 years ago

for anyone who can not access container from port 8181

you have to change the command in /etc/supervisor/conf.d/cloud9.conf in your container
from node /cloud9/server.js --listen 0.0.0.0 -w /workspace
to node /cloud9/server.js --auth ${user}:${pass} --listen 0.0.0.0 -w /workspace

cause cloud9 will listen to localhost when --listen 0.0.0.0 is set and whitout --auth

bdaniel3
2 years ago

This image has stopped working recently. I've become used to using

sudo docker run -it -d -p 8181:8181 -v //:/workspace/ kdelfour/cloud9-docker

as part of provisioning a machine for my default editor and its been working great, but now it will start fine but nothing hosted on port 8181.

vivianmeally
2 years ago

Dont work for me, cannot connect to the docker container. (port 8181)

amuchembled
2 years ago

OK thank you for your answer. I'll try it at release ;)

kdelfour
2 years ago

Cloud9 v2 is no longer maintained. I'm going to migrate to Cloud9 3.0 SDK https://github.com/c9/core and I'm going to try if this problem is still present. I will add apache support after that.