The LinuxServer.io team brings you another container release featuring:

• regular and timely application updates
• easy user mappings (PGID, PUID)
• custom base image with s6 overlay
• weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth
• regular security updates

Find us at:

• Blog - all the things you can do with our containers including How-To guides, opinions and much more!
• Discord - realtime support / chat with the community and the team.
• Discourse - post on our community forum.
• Fleet - an online web interface which displays all of our maintained images.
• GitHub - view the source for all of our repositories.
• Open Collective - please consider helping us by either donating or contributing to our budget

Thelounge (a fork of shoutIRC) is a web IRC client that you host on your own server.

Our images support multiple architectures such as x86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling linuxserver/thelounge should retrieve the correct image for your arch, but you can also pull specific arch images via tags.

The architectures supported by this image are:

Here are some example snippets to help you get started creating a container.

docker create \
  --name=thelounge \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -p 9000:9000 \
  -v </path/to/appdata/config>:/config \
  --restart unless-stopped \
  linuxserver/thelounge

Compatible with docker-compose v2 schemas.

---
version: "2.1"
services:
  thelounge:
    image: linuxserver/thelounge
    container_name: thelounge
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
    volumes:
      - </path/to/appdata/config>:/config
    ports:
      - 9000:9000
    restart: unless-stopped

Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate <external>:<internal> respectively. For example, -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 outside the container.

You can set any environment variable from a file by using a special prepend FILE__.

As an example:

-e FILE__PASSWORD=/run/secrets/mysecretpassword

Will set the environment variable PASSWORD based on the contents of the /run/secrets/mysecretpassword file.

When using volumes (-v flags) permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user PUID and group PGID.

Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.

In this instance PUID=1000 and PGID=1000, to find yours use id user as below:

  $ id username
    uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)

• To log in to the application, browse to https://:9000.
• To setup user account(s) edit /config/config.json
• Change the value public: true, to public: false,
• restart the container and enter the following from the command line of the host:
• docker exec -it thelounge thelounge add <user>
• Enter a password when prompted, refresh your browser.
• You should now be prompted for a password on the webinterface.

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.

• Shell access whilst the container is running: docker exec -it thelounge /bin/bash
• To monitor the logs of the container in realtime: docker logs -f thelounge
• container version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' thelounge
• image version number
  • docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/thelounge

Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.

Below are the instructions for updating containers:

• Update the image: docker pull linuxserver/thelounge
• Stop the running container: docker stop thelounge
• Delete the container: docker rm thelounge
• Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
• Start the new container: docker start thelounge
• You can also remove the old dangling images: docker image prune

• Update all images: docker-compose pull
  • or update a single image: docker-compose pull thelounge
• Let compose update all containers as necessary: docker-compose up -d
  • or update a single container: docker-compose up -d thelounge
• You can also remove the old dangling images: docker image prune

• Pull the latest image at its tag and replace it with the same env variables in one run:

  docker run --rm \
  -v /var/run/docker.sock:/var/run/docker.sock \
  containrrr/watchtower \
  --run-once thelounge
  

Note: We do not endorse the use of Watchtower as a solution to automated updates of existing Docker containers. In fact we generally discourage automated updates. However, this is a useful tool for one-time manual updates of containers where you have forgotten the original parameters. In the long term, we highly recommend using Docker Compose.

• You can also remove the old dangling images: docker image prune

If you want to make local modifications to these images for development purposes or just to customize the logic:

git clone https://github.com/linuxserver/docker-thelounge.git
cd docker-thelounge
docker build \
  --no-cache \
  --pull \
  -t linuxserver/thelounge:latest .

The ARM variants can be built on x86_64 hardware using multiarch/qemu-user-static

docker run --rm --privileged multiarch/qemu-user-static:register --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.

• 19.12.19: - Rebasing to alpine 3.11.
• 28.06.19: - Rebasing to alpine 3.10.
• 15.05.19: - Update Arm variant images to build sqlite3 module.
• 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
• 22.02.19: - Rebasing to alpine 3.9.
• 28.01.19: - Add pipeline logic and multi arch.
• 25.08.18: - Use global install, simplifies adding users.
• 20.08.18: - Rebase to alpine 3.8.
• 06.01.18: - Rebase to alpine 3.7.
• 26.05.17: - Rebase to alpine 3.6.
• 06.02.17: - Rebase to alpine 3.5.
• 14.10.16: - Bump to pickup 2.10 release.
• 14.10.16: - Add version layer information.
• 11.09.16: - Add layer badges to README.
• 31.08.16: - Initial Release.