linuxserver / docker-chromium

Web accessible Chromium inside an Alpine Container
GNU General Public License v3.0
93 stars 29 forks source link

[BUG] Wayland `Failed to open the display from the DISPLAY environment variable.` #13

Closed ghost closed 10 months ago

ghost commented 11 months ago

Is there an existing issue for this?

Current Behavior

I can't connect to the port on http://localhost:<port-number>.

Expected Behavior

No response

Steps To Reproduce

  1. Run Wayland
  2. create and attempt launching the container

Environment

- OS: Fedora 38
- How docker service was installed: via DNF (or ships with Fedora)

CPU architecture

x86-64

Docker creation

---
version: "2.1"
services:
  chromium:
    image: lscr.io/linuxserver/chromium:latest
    container_name: chromium
    security_opt:
      - seccomp:unconfined #optional
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
#      - CHROME_CLI=https://www.linuxserver.io/ #optional
#    volumes:
#      - /path/to/config:/config
    ports:
      - 4000:4000
      - 4001:4001
    shm_size: "4gb"
    restart: unless-stopped

Container logs

[custom-init] No custom files found, skipping...
[ls.io-init] done.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Xvnc KasmVNC 1.1.0 - built Aug  5 2023 18:48:12
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation
Obt-Message: Xinerama extension is not present on the server
github-actions[bot] commented 11 months ago

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

thelamer commented 11 months ago

whats port 4000 for?