The LinuxServer.io team brings you another container release featuring:
- regular and timely application updates
- easy user mappings (PGID, PUID)
- custom base image with s6 overlay
- weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
- regular security updates
Find us at:
- Blog - all the things you can do with our containers including How-To guides, opinions and much more!
- Discord - realtime support / chat with the community and the team.
- Discourse - post on our community forum.
- Fleet - an online web interface which displays all of our maintained images.
- GitHub - view the source for all of our repositories.
- Open Collective - please consider helping us by either donating or contributing to our budget
This image is deprecated. We will not offer support for this image and it will not be updated. We recommend looking at our code-server and openvscode-server containers as potential replacements. https://github.com/linuxserver/docker-code-server https://github.com/linuxserver/docker-openvscode-server
Cloud9 Cloud9 is a complete web based IDE with terminal access. This container is for running their core SDK locally and developing plugins.
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/cloud9:latest should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Available | Tag |
|---|---|---|
| x86-64 | ✅ | amd64-<version tag> |
| arm64 | ✅ | arm64v8-<version tag> |
| armhf | ✅ | arm32v7-<version tag> |
This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Available | Description |
|---|---|---|
| latest | ✅ | Docker and Compose environment pre-installed |
| go | ✅ | Basic Golang environment pre-installed |
| nodejs | ✅ | Current stable NodeJS/NPM environment pre-installed |
| python | ✅ | Current Python3 environment pre-installed |
| ruby | ✅ | Current Ruby environment pre-installed |
Access the webui at http://your-ip:8000, for more information check out here.
Here are some example snippets to help you get started creating a container.
docker-compose (recommended, click here for more info)
---
version: "2.1"
services:
cloud9:
image: lscr.io/linuxserver/cloud9:latest
container_name: cloud9
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/London
- GITURL=https://github.com/linuxserver/docker-cloud9.git #optional
- USERNAME= #optional
- PASSWORD= #optional
volumes:
- /path/to/your/code:/code #optional
- /var/run/docker.sock:/var/run/docker.sock #optional
ports:
- 8000:8000
restart: unless-stoppeddocker cli (click here for more info)
docker run -d \
--name=cloud9 \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e GITURL=https://github.com/linuxserver/docker-cloud9.git `#optional` \
-e USERNAME= `#optional` \
-e PASSWORD= `#optional` \
-p 8000:8000 \
-v /path/to/your/code:/code `#optional` \
-v /var/run/docker.sock:/var/run/docker.sock `#optional` \
--restart unless-stopped \
lscr.io/linuxserver/cloud9:latestContainer images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.
| Parameter | Function |
|---|---|
-p 8000 |
The port for the Cloud9 web interface |
-e PUID=1000 |
for UserID - see below for explanation |
-e PGID=1000 |
for GroupID - see below for explanation |
-e TZ=Europe/London |
Specify a timezone to use EG Europe/London |
-e GITURL=https://github.com/linuxserver/docker-cloud9.git |
Specify a git repo to checkout on first startup |
-e USERNAME= |
Optionally specify a username for http auth |
-e PASSWORD= |
Optionally specify a password for http auth (if USERNAME and PASSWORD are not set, there will be no http auth) |
-v /code |
Optionally if you want to mount up a local folder of code instead of checking out |
-v /var/run/docker.sock |
Needed if you plan to use Docker or compose commands |
You can set any environment variable from a file by using a special prepend FILE__.
As an example:
-e FILE__PASSWORD=/run/secrets/mysecretpasswordWill set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance PUID=1000 and PGID=1000, to find yours use id user as below:
$ id username
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
- Shell access whilst the container is running:
docker exec -it cloud9 /bin/bash - To monitor the logs of the container in realtime:
docker logs -f cloud9 - container version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' cloud9
- image version number
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/cloud9:latest
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:
- Update all images:
docker-compose pull- or update a single image:
docker-compose pull cloud9
- or update a single image:
- Let compose update all containers as necessary:
docker-compose up -d- or update a single container:
docker-compose up -d cloud9
- or update a single container:
- You can also remove the old dangling images:
docker image prune
- Update the image:
docker pull lscr.io/linuxserver/cloud9:latest - Stop the running container:
docker stop cloud9 - Delete the container:
docker rm cloud9 - Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) - You can also remove the old dangling images:
docker image prune
-
Pull the latest image at its tag and replace it with the same env variables in one run:
docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ containrrr/watchtower \ --run-once cloud9
-
You can also remove the old dangling images:
docker image prune
Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.
- We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-cloud9.git
cd docker-cloud9
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/cloud9:latest .The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static
docker run --rm --privileged multiarch/qemu-user-static:register --resetOnce registered you can define the dockerfile to use with -f Dockerfile.aarch64.
- 23.06.22: - Deprecate image.
- 24.06.21: - Use prebuilt compose binaries for the linuxserver repo.
- 07.02.20: - Add optional http auth.
- 02.06.19: - Initial Release.
