search

linuxserver / docker-webtop

Ubuntu, Alpine, Arch, and Fedora based Webtop images, Linux in a web browser supporting popular desktop environments.
GNU General Public License v3.0
1.77k stars 175 forks source link

[BUG] can't build container with custom /config files #191

Closed notkudu closed 9 months ago

notkudu commented 9 months ago

Is there an existing issue for this?

Current Behavior

when I build the container (branch arch-kde) I add extra repos and install extra pkgs and everything sems fine but the second I try to more anything into /config (COPY /anything /config) they don't show up in the image it's like /config is being overwriten. but I can COPY files to any place no program

Expected Behavior

when I COPY files/folder into /config they should be here in the final image

Steps To Reproduce

this is the Dockerfile

FROM ghcr.io/linuxserver/baseimage-kasmvnc:arch

RUN \
  echo "**** install packages ****" && \
  pacman -Sy --noconfirm --needed wget git && \
  mv /etc/pacman.conf pacman.conf.backup && \
  wget -O /etc/pacman.conf "https://raw.githubusercontent.com/xerolinux/xero-fixes/main/conf/pacman.conf" && \
  wget -O /etc/pacman.d/xero-mirrorlist "https://raw.githubusercontent.com/xerolinux/xerolinux-mirrorlist/main/etc/pacman.d/xero-mirrorlist" && \
  pacman -Syu --noconfirm && \
  echo "**** install packages ****" && \
  pacman -Sy --noconfirm --needed \
    dolphin \
    kate \
    lsb-release \
    lsscsi \
    lua \
    lynx \
    man-db \
    man-pages \
    mc \
    mkinitcpio-archiso \
    mkinitcpio-nfs-utils \
    nbd \
    ndisc6 \
    nfs-utils \
    xorg-fonts-alias-misc \
    ttf-unifont \
    xorg-fonts-misc \
    libertinus-font \
    tex-gyre-fonts \
    ttf-fira-code \
    ttf-hack-nerd \
    adobe-source-sans-fonts \
    awesome-terminal-fonts \
    ttf-jetbrains-mono-nerd \
    ttf-ubuntu-font-family \
    expac \
    konsole \
    plasma-desktop && \
  echo "**** application tweaks ****" && \
  echo "**** kde tweaks ****" && \
  sed -i \
    's/applications:org.kde.discover.desktop,/applications:org.kde.konsole.desktop,/g' \
    /usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/config/main.xml && \
  echo "**** cleanup ****" && \
  rm -rf \
    /config/.cache \
    /tmp/* \
    /var/cache/pacman/pkg/* \
    /var/lib/pacman/sync/*

# add local files
COPY /root /
COPY /config /config

# ports and volumes
EXPOSE 3000

VOLUME /config

and then I build like this sudo docker build -t xeroweb:latest . and the build does go throw and seems to work, it's just the files inside /config are missing

Environment

- OS:Debian
- How docker service was installed: pkgs manager

CPU architecture

x86-64

Docker creation

sudo docker run -d --name=xeroweb --security-opt seccomp=unconfined -e PUID=1000 -e PGID=1000 -e TZ=Etc/UTC -p 3389:3389 -v /var/run/docker.sock:/var/run/docker.sock -v /home/kudu/docker/xeroweb:/config --restart unless-stopped xeroweb:latest

Container logs

[migrations] started
[migrations] no migrations found
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____ 
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____  
      | __  |  |  | |  |  |    \ 
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/ 
  Based on images from linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    1000
User GID:    1000
───────────────────────────────────────
[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 Nov 17 2023 17:24: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
[ls.io-init] done.
2023/11/18 16:52:39 [warn] 179#179: could not build optimal types_hash, you should increase either types_hash_max_size: 1024 or types_hash_bucket_size: 64; ignoring types_hash_bucket_size
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
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
 2023-11-18 16:52:44,316 [INFO] websocket 0: got client connection from 127.0.0.1
 2023-11-18 16:52:44,342 [PRIO] Connections: accepted: @10.0.0.213_1700326364.316906::websocket
github-actions[bot] commented 9 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.

thespad commented 9 months ago

This is not a container issue, it's a Container issue. You're copying files to /config inside the container, which is the replaced with your host mount for /config at runtime. If you want files to exist in /config you need to create/copy them at runtime.