Portainer Templates logo

Portainer Templates

Qemu-static Qemu-static

Docker

This container needs special attention. Please check https://hub.docker.com/r/linuxserver/qemu-static for details.

Image details

Pulls: 298k
Architectures: amd64, arm64
Image size: 110 MB
Latest: 10.0.2
User: linuxserverci
Created: Oct 22, 2024
Updated: 28 days ago
Status: active

Configuration

Type
Container
Platform
linux
Image
linuxserver/qemu-static:latest
Ports
80:80/tcp
Volumes
/config : /srv/lsio/qemu-static/config
Env vars
PUID=1000PGID=1000TZ=Etc/UTC
Restart
unless-stopped

Template by technorabilia

Notes

Portainer App Templates by Technorabilia, based on data provided by LinuxServer.io.

Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.

mkdir -p /srv/lsio/qemu-static/config

Installation

  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 the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

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

docker run -d --name Qemu-static \
  -p 80:80/tcp \
  -e 'PUID=1000' \
  -e 'PGID=1000' \
  -e 'TZ=Etc/UTC' \
  -v /srv/lsio/qemu-static/config:/config \
  --restart=unless-stopped \
  linuxserver/qemu-static:latest

Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.

services:
  qemu-static:
    image: linuxserver/qemu-static:latest
    ports:
      - 80:80/tcp
    volumes:
      - /srv/lsio/qemu-static/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
    restart: unless-stopped

Save this file as qemu-static-stack.yml, then from a manager node, run docker stack deploy -c qemu-static-stack.yml qemu-static

version: '3.8'
services:
  qemu-static:
    image: linuxserver/qemu-static:latest
    ports:
      - 80:80/tcp
    volumes:
      - /srv/lsio/qemu-static/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

qemu-static-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: qemu-static
  labels:
    app: qemu-static
spec:
  replicas: 1
  selector:
    matchLabels:
      app: qemu-static
  template:
    metadata:
      labels:
        app: qemu-static
    spec:
      containers:
        - name: qemu-static
          image: linuxserver/qemu-static:latest
          env:
            - name: PUID
              value: '1000'
            - name: PGID
              value: '1000'
            - name: TZ
              value: Etc/UTC
          ports:
            - containerPort: 80
              protocol: TCP
          volumeMounts:
            - name: qemu-static-data-0
              mountPath: /config
      volumes:
        - name: qemu-static-data-0
          hostPath:
            path: /srv/lsio/qemu-static/config

qemu-static-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: qemu-static
spec:
  type: LoadBalancer
  selector:
    app: qemu-static
  ports:
    - name: 80-tcp
      port: 80
      targetPort: 80
      protocol: TCP

Save this file as ~/.config/containers/systemd/qemu-static.container

[Unit]
Description=Qemu-static

[Container]
Image=linuxserver/qemu-static:latest
ContainerName=qemu-static
PublishPort=80:80/tcp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Volume=/srv/lsio/qemu-static/config:/config

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start qemu-static

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

linuxserver.io
Blog Discord Discourse Fleet GitHub Open Collective
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.
  • Open Collective - please consider helping us by either donating or contributing to our budget

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build
QEMU Static - Run multiple architectures of Docker containers on an x8664 or aarch64 host using QEMU static.
qemu-static

Supported Architectures

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/qemu-static: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-\ | | arm64 | ✅ | arm64v8-\ |

Usage

Unlike most of our container library this image is meant to be run ephemerally from the command line to enable the underlying host to run containers built for different architechtures. Changes will not persist a host reboot.

Enable and reset

docker run --rm -it \
  --privileged \
  linuxserver/qemu-static \
  --reset \
  -p yes

Versions

  • 17.11.25: - Use Debian Trixie for build.
  • 09.12.24: - Upgrade to 9.1.2, automate new builds.
  • 07.11.24: - Upgrade to 9.1.1, switch to new debian package and bin naming scheme.
  • 14.10.24: - Initial release.

Serve Qemu-static 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 qemu-static.example.com to http://Qemu-static:80

Add this to your Caddyfile

qemu-static.example.com {
	reverse_proxy http://Qemu-static:80
}

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 Qemu-static
  • 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:80 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :80
  • Stop the other service, or pick a different host port. In 80:80 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:80. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, Qemu-static can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 80

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 /srv/lsio/qemu-static/config
  • Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull linuxserver/qemu-static: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
  • 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 Qemu-static --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.

Similar apps

Docker Container Stats Docker Container Stats Docker Lazytainer DockerModmanager Modmanager DockerRegistry Registry DockerRegistry (cache) Registry (cache) DockerSocket-proxy Socket-proxy DockerWatchtower {shmolf} Watchtower {shmolf} Docker