You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting SUBFOLDER=/doublecommander/ (both slashes included), you get a html plain text like this one: "Cannot GET /doublecommander/". If I remove SUBFOLDER=..., then I can access to container.
Expected Behavior
Get the UI with proper base URL.
Steps To Reproduce
Adding SUBFOLDER=/doublecommander/ to yaml
Environment
- OS: OMV 7.0.4-2 (Sandworm)
- How docker service was installed: omv-extras, compose included
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 100
───────────────────────────────────────
[custom-init] No custom files found, skipping...
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Xvnc KasmVNC 1.2.0 - built Mar 16 2024 19:09:02
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
[ls.io-init] done.
Obt-Message: Xinerama extension is not present on the server
SystemLocale en_US
SystemLanguage en
SystemEncoding UTF-8
DefaultSystemCodePage 65001
DefaultFileSystemCodePage 65001
DefaultRTLFileSystemCodePage 65001
XInitThreads: 1
Starting GuiMessageQueue
Starting Double Commander
Double Commander 1.0.10
Revision: 239
Commit: d00f8b7b7
Build: 2023/02/11
Lazarus: 2.2.4.0
Free Pascal: 3.2.2
Platform: x86_64-Linux-gtk2
System: Debian 12.5
Desktop Environment: Unknown
Widgetset library: GTK 2.24.33
This program is free software released under terms of GNU GPL 2
(C)opyright 2006-2023 Alexander Koblov (alexx2000@mail.ru)
and contributors (see about dialog)
Executable directory: /usr/lib/doublecmd/
Loading configuration from /config/.config/doublecmd/
Loading lng file: /usr/lib/doublecmd/language/doublecmd.en.po
Error loadSystemLocale en_US
SystemLanguage en
SystemEncoding UTF-8
DefaultSystemCodePage 65001
DefaultFileSystemCodePage 65001
DefaultRTLFileSystemCodePage 65001
ing configuration file /config/.config/doublecmd/favoritetabs.xml
PollThread: Start polling
PollThread: AddPoll 10
Creating PixmapManager
Loading icon theme DCTheme
Loading icon theme DCTheme
Error: pixmap [/usr/lib/doublecmd/doublecmd] not loaded!
Creating TFileSystemFileSource
TColumnsFileView.Create components
TColumnsFileView.Create components
UDisks: Cannot acquire connection to DBUS system bus: org.freedesktop.DBus.Error.FileNotFound Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
PollThread: AddPoll 16
UDev: Begin monitoring
FileSystemWatcher thread starting
Detecting mounts through /proc/self/mounts
PollThread: AddPoll 17
Error loading configuration file /config/.config/doublecmd/highlighters.xml
The text was updated successfully, but these errors were encountered:
Closing due to inactivity, I'm presuming you are not actually RP'ing this application leading to it behaving weirdly when setting this environment.
Would recommend trying to access it without that subfolder being set and seeing how you get on. Then try the RP. Join us in Discord for further support with using our containers.
Is there an existing issue for this?
Current Behavior
When setting SUBFOLDER=/doublecommander/ (both slashes included), you get a html plain text like this one: "Cannot GET /doublecommander/". If I remove SUBFOLDER=..., then I can access to container.
Expected Behavior
Get the UI with proper base URL.
Steps To Reproduce
Adding SUBFOLDER=/doublecommander/ to yaml
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: