diff --git a/images/docker-davos/index.html b/images/docker-davos/index.html index fde432ffb8..d163208931 100644 --- a/images/docker-davos/index.html +++ b/images/docker-davos/index.html @@ -1,4 +1,4 @@ - davos - LinuxServer.io
Skip to content

linuxserver/davos

Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI

Davos is an FTP automation tool that periodically scans given host locations for new files. It can be configured for various purposes, including listening for specific files to appear in the host location, ready for it to download and then move, if required. It also supports completion notifications as well as downstream API calls, to further the workflow.

davos

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.

Simply pulling lscr.io/linuxserver/davos:latest 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:

Architecture Available Tag
x86-64 ✅ amd64-<version tag>
arm64 ✅ arm64v8-<version tag>
armhf ❌

Application Setup

The application does not require any set up other than starting the docker container. Further documentation can be found on the davos GitHub repository page.

Read-Only Operation

This image can be run with a read-only container filesystem. For details please read the docs.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+ davos - LinuxServer.io      
 
 
  
 
  
 
 
 
 
  
 
 
 
 
 
  
 
 
 
 
   
linuxserver/davos
 
Scarf.io pulls GitHub Stars GitHub Release GitHub Package Repository GitLab Container Registry Quay.io Docker Pulls Docker Stars Jenkins Build LSIO CI
 
Davos is an FTP automation tool that periodically scans given host locations for new files. It can be configured for various purposes, including listening for specific files to appear in the host location, ready for it to download and then move, if required. It also supports completion notifications as well as downstream API calls, to further the workflow.
 
davos
 
Supported Architectures
 
We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
 
Simply pulling lscr.io/linuxserver/davos:latest 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:
 
  
 Architecture Available Tag 
   
 x86-64 ✅ amd64-<version tag> 
 
 arm64 ✅ arm64v8-<version tag> 
 
 armhf ❌  
  
 
Application Setup
 
The application does not require any set up other than starting the docker container. Further documentation can be found on the davos GitHub repository page.
 
Read-Only Operation
 
This image can be run with a read-only container filesystem. For details please read the docs.
 
Usage
 
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
 
 
Info
 
Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.
 
  
---
 services:
   davos:
     image: lscr.io/linuxserver/davos:latest
@@ -23,7 +23,7 @@
   -v /path/to/downloads/folder:/download \
   --restart unless-stopped \
   lscr.io/linuxserver/davos:latest
-
 
Parameters
 
Containers 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.
 
Ports (-p)
 
  
 Parameter Function 
   
 8080 This is the default port that davos runs under 
  
 
Environment Variables (-e)
 
  
 Env Function 
   
 PUID=1000 for UserID - see below for explanation 
 
 PGID=1000 for GroupID - see below for explanation 
 
 TZ=Etc/UTC specify a timezone to use, see this list. 
  
 
Volume Mappings (-v)
 
  
 Volume Function 
   
 /config davos's config location. This is where it stores its database file and logs. 
 
 /download davos's file download location 
  
 
Miscellaneous Options
 
  
 Parameter Function 
   
   
  
 
Environment variables from files (Docker secrets)
 
You can set any environment variable from a file by using a special prepend FILE__.
 
As an example:
 
-e FILE__MYVAR=/run/secrets/mysecretvariable
+
 
Parameters
 
Containers 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.
 
Ports (-p)
 
  
 Parameter Function 
   
 8080:8080 This is the default port that davos runs under 
  
 
Environment Variables (-e)
 
  
 Env Function 
   
 PUID=1000 for UserID - see below for explanation 
 
 PGID=1000 for GroupID - see below for explanation 
 
 TZ=Etc/UTC specify a timezone to use, see this list. 
  
 
Volume Mappings (-v)
 
  
 Volume Function 
   
 /config davos's config location. This is where it stores its database file and logs. 
 
 /download davos's file download location 
  
 
Miscellaneous Options
 
  
 Parameter Function 
   
 --read-only=true Run container with a read-only filesystem. Please read the docs. 
  
 
Environment variables from files (Docker secrets)
 
You can set any environment variable from a file by using a special prepend FILE__.
 
As an example:
 
-e FILE__MYVAR=/run/secrets/mysecretvariable
 
 
Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.
 
Umask for running applications
 
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.
 
User / Group Identifiers
 
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 your_user as below:
 
id your_user
 
 
Example output:
 
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
 
 
Docker Mods
 
Docker Mods Docker Universal Mods
 
We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
 
Support Info
 
     
  •  
    Shell access whilst the container is running:
     
    docker exec -it davos /bin/bash
@@ -46,4 +46,4 @@
   --pull \
   -t lscr.io/linuxserver/davos:latest .
 
     
    The ARM variants can be built on x86_64 hardware and vice versa using lscr.io/linuxserver/qemu-static
     
    docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset
-
     
    Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
     
    Versions
     
       
    • 24.06.24: - Rebase to Alpine 3.20.
      •  
    • 20.03.24: - Rebase to Alpine 3.19.
      •  
    • 12.07.23: - Rebase to Alpine 3.18.
      •  
    • 07.07.23: - Deprecate armhf. As announced here
      •  
    • 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
      •  
    • 15.01.22: - Rebasing to alpine 3.15.
      •  
    • 01.06.20: - Rebasing to alpine 3.12.
      •  
    • 19.12.19: - Rebasing to alpine 3.11.
      •  
    • 28.06.19: - Rebasing to alpine 3.10.
      •  
    • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
      •  
    • 22.03.19: - Updating runtime deps due to change in OpenJRE.
      •  
    • 08.03.19: - Updating build environment to pass proper build flags and use gradle wrapper.
      •  
    • 22.02.19: - Rebasing to alpine 3.9.
      •  
    • 18.11.16: - Initial Release.
      •  
      
 
  
  
  
 
 
 
      
\ No newline at end of file
+

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

Versions

  • 24.06.24: - Rebase to Alpine 3.20.
  • 20.03.24: - Rebase to Alpine 3.19.
  • 12.07.23: - Rebase to Alpine 3.18.
  • 07.07.23: - Deprecate armhf. As announced here
  • 13.02.23: - Rebase to Alpine 3.17, migrate to s6v3.
  • 15.01.22: - Rebasing to alpine 3.15.
  • 01.06.20: - Rebasing to alpine 3.12.
  • 19.12.19: - Rebasing to alpine 3.11.
  • 28.06.19: - Rebasing to alpine 3.10.
  • 23.03.19: - Switching to new Base images, shift to arm32v7 tag.
  • 22.03.19: - Updating runtime deps due to change in OpenJRE.
  • 08.03.19: - Updating build environment to pass proper build flags and use gradle wrapper.
  • 22.02.19: - Rebasing to alpine 3.9.
  • 18.11.16: - Initial Release.
\ No newline at end of file diff --git a/images/docker-limnoria/index.html b/images/docker-limnoria/index.html index 851bba31eb..abcc950c62 100644 --- a/images/docker-limnoria/index.html +++ b/images/docker-limnoria/index.html @@ -5,7 +5,7 @@ supybot.directories.data.web: /config/web supybot.directories.log: /config/logs supybot.directories.plugins: /config/plugins -

NOTE: These are not grouped together in the file. You will need to search your conf file for the variables.

Then place your conf file and any of your existing directories in /config and start up the container.

Plugin Requirements

The container will pip install any requirements.txt it finds in the /config/plugins folder on startup.

If you install a plugin using the PluginDownloader that includes a requirements.txt you can execute a shell into the container and then use pip install /config/plugins/ThePlugin/requirements.txt or restart the container and the requirements will be installed.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

---
+

NOTE: These are not grouped together in the file. You will need to search your conf file for the variables.

Then place your conf file and any of your existing directories in /config and start up the container.

Plugin Requirements

The container will pip install any requirements.txt it finds in the /config/plugins folder on startup.

If you install a plugin using the PluginDownloader that includes a requirements.txt you can execute a shell into the container and then use pip install /config/plugins/ThePlugin/requirements.txt or restart the container and the requirements will be installed.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.

Info

Unless a parameter is flaged as 'optional', it is mandatory and a value must be provided.

---
 services:
   limnoria:
     image: lscr.io/linuxserver/limnoria:latest
@@ -28,7 +28,7 @@
   -v /path/to/limnoria/config:/config \
   --restart unless-stopped \
   lscr.io/linuxserver/limnoria:latest
-

Parameters

Containers 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.

Ports (-p)

Parameter Function
8080 Port for Limnoria's web interface.

Environment Variables (-e)

Env Function
PUID=1000 for UserID - see below for explanation
PGID=1000 for GroupID - see below for explanation
TZ=Etc/UTC specify a timezone to use, see this list.

Volume Mappings (-v)

Volume Function
/config Persistent config files

Miscellaneous Options

Parameter Function

Environment variables from files (Docker secrets)

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

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable
+

Parameters

Containers 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.

Ports (-p)

Parameter Function
8080:8080 Port for Limnoria's web interface.

Environment Variables (-e)

Env Function
PUID=1000 for UserID - see below for explanation
PGID=1000 for GroupID - see below for explanation
TZ=Etc/UTC specify a timezone to use, see this list.

Volume Mappings (-v)

Volume Function
/config Persistent config files

Miscellaneous Options

Parameter Function

Environment variables from files (Docker secrets)

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

As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

User / Group Identifiers

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 your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

Docker Mods Docker Universal Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info