From 49258ee7ddee36ea8eb92ec5305b0b2c54ed698f Mon Sep 17 00:00:00 2001 From: aptalca Date: Sun, 4 Mar 2018 22:55:18 -0500 Subject: [PATCH] Update README.md --- README.md | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 8fe6d21..bfd1273 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,6 @@ Even automatically sent them weekly newsletters of new content that has been add ``` docker create \ --name=ombi \ - -v /etc/localtime:/etc/localtime:ro \ -v :/config \ -e PGID= -e PUID= \ -e TZ= \ @@ -53,17 +52,12 @@ http://192.168.x.x:8080 would show you what's running INSIDE the container on po * `-p 3579` - the port(s) -* `-v /etc/localtime` for timesync - see [Localtime](#localtime) for important information -* `-e TZ` for timezone information, Europe/London - see [Localtime](#localtime) for important information +* `-e TZ` for timezone information, Europe/London * `-v /config` - where ombi should store its config files * `-e PGID` for GroupID - see below for explanation * `-e PUID` for UserID - see below for explanation It is based on ubuntu xenial with s6 overlay, for shell access whilst the container is running do `docker exec -it ombi /bin/bash`. - -## Localtime - -It is important that you either set `-v /etc/localtime:/etc/localtime:ro` or the TZ variable, mono will throw exceptions without one of them set. ### User / Group Identifiers @@ -95,6 +89,7 @@ Webui is at `:3579`, Follow the setup wizard on initial install. Then ## Versions ++ **05.03.18:** Switch to Ombi v3 stable based on .net core. V3 uses a different database structure so the user has to set up from scratch again. V2 settings are not lost by updating; the user can go back to v2 with old settings and data by pulling image tag 64 + **26.01.18:** Fix continuation lines. + **16.04.17:** Switch to using inhouse mono baseimage. + **17.02.17:** Initial Release.