deon/spdocker
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add setting container timezone for servers

Browse Source
This commit is contained in:
Deon George 2018-03-21 16:36:33 +11:00
parent 244fbfa243
commit 1d5077d825
No known key found for this signature in database
GPG Key ID: 7670E8DC27415254
2 changed files with 14 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
source/server/index.md
View File

@ -132,6 +132,19 @@ ENTRYPOINT [ "/sbin/init" ]
CMD [ "start" ] CMD [ "start" ]
``` ```
### Set your container timezone (optional)
If you want your running container to be in your timezone, then add this to your Dockerfile
```Dockerfile
# Set out local time
RUN ln -sf /usr/share/zoneinfo/Australia/Melbourne /etc/localtime
```
<small>**NOTE**: This will set your timezone to Melbourne, Australia - naturally, choose the appropriate Country/City for your timezone.
## Build your Image
A complete Dockerfile is available [here](http://dev.leenooks.net/deon/spdocker/blob/master/Dockerfile) if you need one as a starting point. Once you have your images loaded on a web server, and the supporting build files run `docker build -t ibm/spectrumprotect:8.1.x .` A complete Dockerfile is available [here](http://dev.leenooks.net/deon/spdocker/blob/master/Dockerfile) if you need one as a starting point. Once you have your images loaded on a web server, and the supporting build files run `docker build -t ibm/spectrumprotect:8.1.x .`
If your final build is successful, you should see a Docker Image that is about 3GB. If your final build is successful, you should see a Docker Image that is about 3GB.

2
source/server/upgrade.md
View File

@ -84,7 +84,7 @@ ANS8002I Highest return code was 0.
While you can control the timeout between the SIGTERM and SIGKILL signal and you can even control which kill signal is sent, I haven't explored what signals SP will act on. So as a recommendation, always use SP `halt` command to stop an SP server.</small> While you can control the timeout between the SIGTERM and SIGKILL signal and you can even control which kill signal is sent, I haven't explored what signals SP will act on. So as a recommendation, always use SP `halt` command to stop an SP server.</small>
## If you can, snapshot your persistent storage. ## If you can, snapshot your persistent storage.
If you can snapshot your persistent storage that you provide to the SP Docker Container, that will save you doing a "restoredb" if something goes pair shaped. If you can snapshot your persistent storage that you provide to the SP Docker Container, that will save you doing a "restore db" if something goes pair shaped.
```bash Using LVM Snapshot ```bash Using LVM Snapshot
[root@host]# df /srv/sp [root@host]# df /srv/sp