Portainer Templates logo

Portainer Templates

Alpine Xfce4 noVNC Alpine Xfce4 noVNC

Container

OtherTools

Alpine xfce4 novnc

Image details

Pulls: 23.8k
Architecture: amd64, arm64, arm/v7
Image size: 420 MB
User: novaspirit
Created: Nov 16, 2022
Updated: 27 days ago
Status: active

Source details

Repo: novaspirit/alpine_xfce4_novnc
Stars: 118
Forks: 49
Language: HTML
Updated: 2 years ago

Configuration

Type
Container
Platform
linux
Image
novaspirit/alpine_xfce4_novnc:latest
Ports
6080:6080/tcp56780:56780/tcp
Volumes
/home/alpine/downloads : /portainer/Files/AppData/Config/alpine-xfce4-novnc/home/alpine/downloads
Restart
unless-stopped

Template by novaspirit

Notes

Template created by Pi-Hosted Series
Check our Github page: https://github.com/pi-hosted/pi-hosted

Official Webpage: https://github.com/novaspirit/Alpine_xfce4_noVNC
Official Docker Documentation: https://github.com/novaspirit/Alpine_xfce4_noVNC


Default username/password will be alpine/alpine.

Standalone Install

Select an install method, to see config/commands for deploying Alpine Xfce4 noVNC

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Alpine Xfce4 noVNC, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see novaspirit/alpine_xfce4_novnc for app-specific guidance.

Alpine xfce4 noVNC

Simple and minimal Alpine Docker Image providing XFCE4 through html5 noVNC connection

GitHub repo size Docker Build Docker Pulls Docker Size
preview

Build Image

git clone https://github.com/novaspirit/Alpine_xfce4_noVNC.git
docker build -t alpine-xfce4 Alpine_xfce4_noVNC/

Run Image

docker run -it -p 6080:6080 --name alpine-novnc alpine-xfce4

Run from Dockerhub

docker run -it -p 6080:6080 --name alpine-novnc novaspirit/alpine_xfce4_novnc

Connect With noVNC

Use modern browswer to connect to http://(docker ip):6080/vnc.html
the predefined password is alpine

LICENCE

MIT

Serve Alpine Xfce4 noVNC on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying alpine-xfce4-novnc.example.com to http://alpine-xfce4-novnc:6080

Add this to your Caddyfile

alpine-xfce4-novnc.example.com {
	reverse_proxy http://alpine-xfce4-novnc:6080
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs alpine-xfce4-novnc
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:6080 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :6080
  • Stop the other service, or pick a different host port. In 6080:6080 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:6080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, alpine-xfce4-novnc can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 6080

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/alpine-xfce4-novnc/home/alpine/downloads

Image won't pull

Test the pull directly on the host: docker pull novaspirit/alpine_xfce4_novnc:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect alpine-xfce4-novnc --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Alpine Xfce4 noVNC runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Alpine Xfce4 noVNC needs bundled into one download. This template pulls novaspirit/alpine_xfce4_novnc:latest, which Docker fetches once (about 420 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Alpine Xfce4 noVNC's comes from Docker Hub, published by novaspirit.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 6080:6080 means it's reachable on port 6080 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 6080:6080
  • 56780:56780

Volumes

A volume is where Alpine Xfce4 noVNC keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /home/alpine/downloads from /portainer/Files/AppData/Config/alpine-xfce4-novnc/home/alpine/downloads on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Alpine Xfce4 noVNC after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Alpine Xfce4 noVNC sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container alpine-xfce4-novnc. That's what you'll spot in the containers list and use in commands like docker logs alpine-xfce4-novnc.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Alpine Xfce4 noVNC up. Add the template list to Portainer once, then deploying Alpine Xfce4 noVNC is a click rather than a wall of config.