Container-based chrome desktop application accessible using VNC client.
100K+
Simple container used to server VNC based chrome browser. Run chrome browser application under a container based on startx/fedora container
:latest : Fedora core 29 + Chrome 50.0.2661.102:fc28 : Fedora core 28 + Chrome 50.0.2661.102:centos7 : CentOS 7 + Chrome:alpine3 : Alpine 3.7 + Chrome 50.0.2661.102docker you can run docker run -it --name="vdi-chrome" startx/vdi-chrome from any docker hostdocker-compose you can create a docker-compose.yml file with the following contentservice:
image: startx/vdi-chrome:latest
container_name: "vdi-chrome"
volumes:
- "/tmp/container/chrome/logs:/logs:z"
- "/tmp/container/chrome/data:/home/chrome:z"
You can use this public image as a base image in your openshift build strategy. You can first import our openshift image stream and automatically add them in your service catalog. You can also test our deploy template or our build and deploy template
# import image streams
oc create -f https://raw.githubusercontent.com/startxfr/docker-images/master/VDI/chrome/openshift-imageStreams.json
# import deploy template and start a sample application
oc create -f https://raw.githubusercontent.com/startxfr/docker-images/master/VDI/chrome/openshift-template.json
oc process startx-vdi-chrome-template | oc create -f -
# import build and deploy template and start a sample application
oc create -f https://raw.githubusercontent.com/startxfr/docker-images/master/VDI/chrome/openshift-template-build.json
oc process startx-vdi-chrome-build-template | oc create -f -
You can use this image as an s2i builder image.
s2i build https://github.com/startxfr/docker-images-example-chrome startx/vdi-chrome test-chrome
docker run --rm -i -t test-chrome
service:
image: startx/vdi-chrome:latest
container_name: "vdi-chrome"
ports:
- "1000:5900"
service:
image: startx/vdi-chrome:latest
container_name: "vdi-chrome"
expose:
- "5900"
data:
image: startx/fedora:latest
container_name: "vdi-chrome-data"
service:
image: startx/vdi-chrome:latest
container_name: "vdi-chrome"
volume_from:
- data:rw
You can use this Dockerfile template to start a new personalized container based on this container. Create a file named Dockerfile in your project directory and copy this content inside. See docker guide for instructions on how to use this file.
FROM startx/vdi-chrome:latest
#... your container specifications
CMD ["/bin/sx", "run"]
This container is based on startx fedora container who came with some additional environment variable
| Variable | Type | Mandatory | Description |
|---|---|---|---|
| base image environement | see environment list | ||
| SERVER_NAME | string | no | Server name for this container. If no name localhost will be assigned |
| HOSTNAME | auto | auto | Container unique id automatically assigned by docker daemon at startup |
| LOG_PATH | auto | auto | default set to /logs and used as a volume mountpoint |
| APP_PATH | auto | auto | default set to /data and used as a volume mountpoint |
| SX_CHROME_SCREEN_RES_X | 1024x768x24 | auto | Define the screen resolution for X server |
| SX_CHROME_SCREEN_RES_CHROME | 1024,768 | auto | Define the screen resolution for Chrome GUI window |
| Port | Description |
|---|---|
| 5900 | standard httpd network port used for non encrypted http traffic |
| Container directory | Description |
|---|---|
| /logs | log directory used to record container and chrome logs |
| /home/chrome | data directory served by chrome. If empty will be filled with app on startup. In other case use content from mountpoint or data volumes |
access to the running Browser with your favorites vnc client vinagre vnc://localhost:5900. Change port and hostname according to your current configuration
You want to use this container and code to build and create locally this container, follow theses instructions.
This section will help you if you want to :
You must have a working environment with the source code of this repository. Read and follow how to setup your working environment to get a working directory. The following instructions assume you are at the top level of your working directory.
dockercd VDI/chromedocker build -t vdi-chrome .docker run -p 5900:5900 -v /data:/home/chrome -it vdi-chrome. If you add a second parameter (like /bin/bash) to will run this command instead of the default entrypoint. Usefull to interact with this container (ex: /bin/bash, /bin/ps -a, /bin/df -h,...)docker run -p 5900:5900 -v /data:/home/chrome -d vdi-chromedocker-composecd VDI/chromedocker-compose up Startup logs appears and escaping this command stop the containerdocker-compose up -d. Container startup logs can be read using docker-compose logsIf you experience trouble with port already used, edit docker-compose.yml file and change port mapping
Content type
Image
Digest
sha256:e29dcc79c…
Size
445.7 MB
Last updated
over 1 year ago
docker pull startx/vdi-chrome