Desired Behavior

I maintain a gPodder docker image based on the Alpine version of this base image. I was hoping to figure out a way to get gPodder to launch with a GTK3 dark theme in the WebUI. I know that some people have been able to get gPodder to run in dark mode by installing a GTK3 dark theme and then setting gtk-application-prefer-dark-theme = true in their gtk settings. I know that I can add a GTK3 dark theme in my Dockerfile (for example apk add materia-dark --repository=http://dl-cdn.alpinelinux.org/alpine/edge/testing/) along with gtk-murrine-engine, but I'm not sure how to change the general GTK configuration so that the app prefers the dark theme (or if this is even possible).

Current Behavior

App launches using default light UI.

Alternatives Considered

I tried installing materia-dark manually in an already running container, but was not able to figure out how to add the setting gtk-application-prefer-dark-mode.

When setting the GUIAUTOSTART environment variable to true, the websocat (in /etc/services.d/autostart/run) command ends up never being ran to launch the application.

I believe this is because IPv6 is enabled, here's a netstat -tulpn output:

(Where :::8080 is the app I'm running.)

I'm caught in this loop:

  until \
    $(true &>/dev/null </dev/tcp/127.0.0.1/3350) && \
    $(true &>/dev/null </dev/tcp/127.0.0.1/4822) && \
    $(true &>/dev/null </dev/tcp/127.0.0.1/${CUSTOM_PORT:=3000}) &&
    $(true &>/dev/null </dev/tcp/127.0.0.1/3389)
  do
    sleep .5
  done

Because port 3350 isn't available on 127.0.0.1, you'd have to connect to ::1 or instead. Or better yet, I propose switching all 127.0.0.1 instances with localhost so this works either way.

Expected Behavior

run should sleep until all ports are available and I'd see the log line:

[guac-init] Auto start set, starting application

Current Behavior

Instead of continuing past that until loop, I see a sleep .5 process in the process list with ever-incrementing PIDs.

If I switch over to localhost (instead of 127.0.0.1), run continues to execute.

Steps to Reproduce

1. Enable IPv6 in your container environment.
2. Install netstat, observe that xrdp-session only listens on IPv6.

Environment

OS: Linux
CPU architecture: x86_64
How docker service was installed: k3s

Command used to create docker container (run/create/compose/screenshot)

This was reproduced with the k8s-at-home/calibre helm cart.

Docker logs

N/A

Allow for using derivative containers to be behind a proxy within a subfolder.

I think the change that needs to happen in https://github.com/linuxserver/gclient but I'm not sure.

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

linuxserver/docker-firefox#16

I have to open the GUI in a web browser, then reconnect using RDP to fix

Expected Behavior

RDP should always work.

Steps To Reproduce

After connecting to this using Microsoft Remote Desktop client, I disconnect. Then connect again after a few minutes. The screen is black.

Environment

n/a

Docker creation

see linked issue

Container logs

n/a