fionnb/picapport Docker 镜像 - 轩辕镜像

NEWS

From version 10.2.0-3 on, the docker image will add the line robot.use.filesystem.monitor=false to your properties config, unless a line with that property already exists. This is to circumvent the problems with filesystem monitor introduced at v9.0.0. IF you did not encounter any problems with versions >9 on your environment, you can set this setting to "true" and it will not be changed back by future image updates.

From version 9.0.0 on this is based on the official ubuntu20.04 minimal. Also, it turns out that from version 9.0.0 the new filesystem monitor does not work properly in most docker environments.

From version 7.3.0 on this is based on the official ubuntu18.04 minimal container, making it a bit smaller.

From version 7.1.2b and upwards, you can set the language and exposed port in a file called "ENV" (case sensitive) in the data directory (see below) that you export to the picapport container. The file must use Unix line breaks and contain the following data:

PICAPPORT_PORT=8888
PICAPPORT_LANG="de"

It will be read upon the start of the picapport container. Please note that the PORT setting will only be used to create an initial properties file if there is none, so it effectively will only be read on the first start. Later on, you will have to adjust the port setting in the picapport properties file. Please consult the picapport documentation for details and possible language settings.

DISCLAIMER

I am not the author of the picapport software and I am providing these images for free, maintaining them in my spare time. Although I test them by heavily using them myself, there is a lot of 3rd party components outside the scope of my control involved. By downloading and using it you agree that I can not be held liable for any problems or damages that might be incurred directly or indirectly by using the software or container.

DESCRIPTION

This is a fairly generic picapport headless application container with raw support based on a minimal ubuntu.

The application base directory inside the container is /opt/picapport

Static data is exported to the following volumes:

• /opt/picapport/photos
  This is where your photos are expected to be. picapport should recognize existing photos automatically. If you upload data to picapport, an "uploads" directory will be created within this directory.

• /opt/picapport/data
  This is where all picapport working data and config resides. If there is no config, a very basic one will be created for you inside this directory on the first start of the container.

The service is running as uid 1000, so your external files in "photos" should belong to this or be readable by this uid.

PREPARATIONS

All lines beginning with "#>" are meant to be entered (without the "#>"!) on a linux Terminal prompt.

• To use the latest known stable version of picapport:
  #> VERSION="stable"

• To use the latest not-so-well-tested release:
  #> VERSION="latest"

• Define a directory where your photos are (or where you want picapport to store its photos).
  #> PHOTOS="/home/$USER/Pictures/"
  Enter this to make sure the photo directory exists!
  #> [ -d "$PHOTOS" ] || mkdir -p "$PHOTOS"

• Define a directory where picapport can store its configs and database. For this you may also use a previously created .picapport directory, just make sure that it is not used by two application instances at the same time!)
  #> PADATA="/home/$USER/.picapport"
  Enter this to make sure the data directory exists!
  #> [ -d "$PADATA" ] || mkdir -p "$PADATA"

STARTING

The following command must be pasted in the Terminal on one line:
#> docker run -d -p 8080:8888 -v "$PHOTOS":/opt/picapport/photos -v "$PADATA":/opt/picapport/data --name picapport fionnb/picapport:$VERSION; docker logs -f picapport

This will download an ubuntu-minimal layer and on top of that the picapport application layer. Download may take several minutes, but only on the first start.

USING

The first start of picapport can take up to 30-60 seconds to initialize all databases. Also, depending on how many pictures the application finds, it may take some time for them to appear in the GUI. Please be patient and have a look at the log output until a log line appears that says:
INFO:oejs.Server:main: Started.
After that, point your browser at "http://localhost:8080/" to access the web GUI of picapport.

STOPPING/RESUMING

You may stop and start your picapport application at any time by issuing the following commands:
#> docker stop picapport
#> docker start picapport

To inspect the output of the picapport application (e.g. for errors) use:
#> docker logs [-f] picapport

ATTENTION

Before you update your picapport version or pull a new release, please make sure that you have stopped (and possibly renamed or removed) any previous version container that you had running! Running TWO picapport instances on the same data directory at the same time is NOT a good idea!