The image has been reworked to use Alpine instead of Ubuntu. As a consequence, the UID of the user that the application process runs under has changed from
999 (which was the default in Ubuntu) to
500. Thereby, if you mount a host directory to persist data and configs, you will need to
chown -R 500:500 your local files before switching to the new version.
1922 (released May 16, 2017).
The image is based on Alpine 3.4 with OpenJDK JRE 8.
Upsource is configured to store all data (including backups, logs and temporary files) under
/var/lib/upsource directory, which is also a Docker volume. In addition,
/opt/upsource/conf directory is used for configuration files.
There are multiple approaches to handling persistent storage with Docker. For detailed information, see Manage data in containers.
If a host directory is used, it should be writable by the application process, which runs as UID
Pull the image, create a new container and start it:
docker pull esycat/upsource docker create --name upsource -p 8080:8080 --restart=always esycat/upsource docker start upsource
Typically, we would like to run the Upsource behind a lightweight HTTP server.
etc/nginx contains an example virtual host configuration for Nginx.
The size of the image is not his vault cause upsource is really huge actually its the smallest size he could do it.
Sorry, I want to know why I set up the container is stop "Upsource PSI Service is running" a long time and cann't continue?
Is there anyway to upgrade this container without losing configurations ?
Dude your images are huge. You really need to read Best Practices of creating Docker images.