Lastest pull of lscr.io/linuxserver/firefox:latest broke firefox/VNC.

[meek2100]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Container shows that it is running fine, but when I try to access it I can't and have a bunch of error. I think the most recent update broke VNC.

Expected Behavior

Run Firefox & VNC on ports 3000 and 3001

Steps To Reproduce

Deploy the docker compose stack below in portainer and then attempt to connect to port 3000 or 3001.

Host Info:

Portainer Host Info:

Docker Compose:

services:
  firefox:
    image: lscr.io/linuxserver/firefox:latest
    container_name: firefox
    #security_opt:
      #- seccomp:unconfined #optional
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      #- FIREFOX_CLI=https://www.linuxserver.io/ #optional
    volumes:
      - firefox_test:/config
    ports:
      - 3000:3000
      - 3001:3001
    shm_size: "1gb"
    restart: unless-stopped

volumes:
  firefox_test:

Environment

- OS:
- How docker service was installed: docker-compose inside of portainer.

Portainer Host info:

CPU architecture

x86-64

Docker creation

Portainer handles this.

Container logs

Here is what I'm seeing in the log.

Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12101012
[ls.io-init] done.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
[mi] mieq: warning: overriding existing handler (nil) with 0x61d673a04930 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x61d673a04930 for event 3
Obt-Message: Xinerama extension is not present on the server
19
MESA: error: ZINK: failed to choose pdev
glx: failed to create drisw screen

[github-actions]

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

[thespad]

I can't replicate this with the latest version of the image but you are running the Snap version of docker which is known to cause various problems. Using your compose:

[meek2100]

@thespad
I migrated from snap docker to vanilla docker and that resolved the issue.

Thanks for pointing out that the snap version of docker is different, I hadn't realized that they were. I was thinking snap was the official one just delivered through Ubuntu's new package manager instead of apt.