The sh in docker sh stands for self hosted folders will be ready for you to run browsers and others stuff the orginal people who made the docker container will be credited.
- Finish making Docker installation on kali linux tutorial
- Finish making docker compose installation on kali linux tutorial
- [ ]
Browsers
Workspace
Docker Installation
things that has nonthing to do with or about this repository
&textColor=rgba(121,121,121,1))
Mozilla Firefox is a free and open-source web browser developed by Mozilla Foundation and its subsidiary, Mozilla Corporate.
Originally Created by: Jlesage
Original Repository: Docker Firefox
Donate to the Original Creator of Docker Firefox
First git clone the this repository
git clone https://github.com/GitXpresso/dockersh.git
Then do
cd Firefox
To start firefox do
docker compose up
Or
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
Chromium Official Github Mirror: chromium
Originally Created by: LinuxServer
Original Repository: Docker Chromium
Creator website: linuxserver.io
Donations : Linux Server Open collective
- Application Setup
- Security
- Options in all KasmVNC based GUI containers
- Language Support - Internationalization
- DRI3 GPU Acceleration
- Nvidia GPU Support
- Application management
- Usage
- Parameters
- Environment variables from files Docker secrets
- Umask for running applications
- User / Group Identifiers
- Docker-Mods
- Support Info
- Building locally
- Versions
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/chromium: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- |
| arm64 | ✅ | arm64v8- |
| armhf | ❌ |
The application can be accessed at:
To Run the selfhosted chromium do the following commands below
Modern GUI desktop apps have issues with the latest Docker and syscall compatibility, you can use Docker with the --security-opt seccomp=unconfined setting to allow these syscalls on hosts with older Kernels or libseccomp*
Warning
Do not put this on the Internet if you do not know what you are doing.
By default this container has no authentication and the optional environment variables CUSTOM_USER and PASSWORD to enable basic http auth via the embedded NGINX server should only be used to locally secure the container from unwanted access on a local network. If exposing this to the Internet we recommend putting it behind a reverse proxy, such as SWAG, and ensuring a secure authentication solution is in place. From the web interface a terminal can be launched and it is configured for passwordless sudo, so anyone with access to it can install and run whatever they want along with probing your local network.
This container is based on Docker Baseimage KasmVNC which means there are additional environment variables and run configurations to enable or disable specific functionality.
- Variable: CUSTOM_PORT
- Description: Internal port the container listens on for http if it needs to be swapped from the default 3000.
- Variable: CUSTOM_HTTPS_PORT
- Description: Internal port the container listens on for https if it needs to be swapped from the default 3001.
- Variable: CUSTOM_USER
- Description: HTTP Basic auth username, abc is default.
- Variable: PASSWORD
- Description: HTTP Basic auth password, abc is default. If unset there will be no auth
- Variable: SUBFOLDER
- Description: Subfolder for the application if running a subfolder reverse proxy, need both slashes IE /subfolder/
- Variable: TITLE
- Description: The page title displayed on the web browser, default "KasmVNC Client".
- Variable: FM_HOME
- Description: This is the home directory (landing) for the file manager, default "/config".
- Variable: START_DOCKER
- Description: If set to false a container with privilege will not automatically start the DinD Docker setup.
- Variable: DRINODE
- Description: If mounting in /dev/dri for DRI3 GPU Acceleration allows you to specify the device to use IE /dev/dri/renderD128
- Variable: DISABLE_IPV6
- Description: If set to true or any value this will disable IPv6
- Variable: LC_ALL
- Description: Set the Language for the container to run as IE fr_FR.UTF-8 ar_AE.UTF-8
- Variable: NO_DECOR
- Description: If set the application will run without window borders in openbox for use as a PWA.
- Variable: NO_FULL
- Description: Do not autmatically fullscreen applications when using openbox.
- Variable: --privileged
- Description: Will start a Docker in Docker (DinD) setup inside the container to use docker in an isolated environment. For increased performance mount the Docker directory inside the container to the host IE -v /home/user/docker-data:/var/lib/docker.
- Variable: -v /var/run/docker.sock:/var/run/docker.sock
- Description: Mount in the host level Docker socket to either interact with it via CLI or use Docker enabled applications.
- Variable: --device /dev/dri:/dev/dri
- Description: Mount a GPU into the container, this can be used in conjunction with the DRINODE environment variable to leverage a host video card for GPU accelerated applications. Only Open Source drivers are supported IE (Intel,AMDGPU,Radeon,ATI,Nouveau)
The environment variable LC_ALL can be used to start this container in a different language than English simply pass for example to launch the Desktop session in French LC_ALL=fr_FR.UTF-8. Some languages like Chinese, Japanese, or Korean will be missing fonts needed to render properly known as cjk fonts, but others may exist and not be installed inside the container depending on what underlying distribution you are running. We only ensure fonts for Latin characters are present. Fonts can be installed with a mod on startup.
To install cjk fonts on startup as an example pass the environment variables (Alpine base):
-e DOCKER_MODS=linuxserver/mods:universal-package-install
-e INSTALL_PACKAGES=fonts-noto-cjk-e LC_ALL=zh_CN.UTF-8
The web interface has the option for "IME Input Mode" in Settings which will allow non english characters to be used from a non en_US keyboard on the client. Once enabled it will perform the same as a local Linux installation set to your locale.
For accelerated apps or games, render devices can be mounted into the container and leveraged by applications using:
--device /dev/dri:/dev/dri
This feature only supports Open Source GPU drivers:
| Driver | Description |
|---|---|
| Intel | i965 and i915 drivers for Intel iGPU chipsets |
| AMD | AMDGPU, Radeon, and ATI drivers for AMD dedicated or APU chipsets |
| NVIDIA | nouveau2 drivers only, closed source NVIDIA drivers lack DRI3 support |
The DRINODE environment variable can be used to point to a specific GPU. Up to date information can be found here
Nvidia support is not compatible with Alpine based images as Alpine lacks Nvidia drivers
Nvidia support is available by leveraging Zink for OpenGL support. This can be enabled with the following run flags:
- Variable: --gpus all
- Description: This can be filtered down but for most setups this will pass the one Nvidia GPU on the system
- Variable: --runtime nvidia
- Description: Specify the Nvidia runtime which mounts drivers and tools in from the host
The compose syntax is slightly different for this as you will need to set nvidia as the default runtime:
sudo nvidia-ctk runtime configure --runtime=docker --set-as-default
sudo service docker restart
And to assign the GPU in compose:
services:
chromium:
image: lscr.io/linuxserver/chromium:latest
deploy:
resources:
reservations:
devices:
- driver: nvidia
count: 1
capabilities: [compute,video,graphics,utility]
If you run system native installations of software IE sudo apt-get install filezilla and then upgrade or destroy/re-create the container that software will be removed and the container will be at a clean state. For some users that will be acceptable and they can update their system packages as well using system native commands like apt-get upgrade. If you want Docker to handle upgrading the container and retain your applications and settings we have created proot-apps which allow portable applications to be installed to persistent storage in the user's $HOME directory and they will work in a confined Docker environment out of the box. These applications and their settings will persist upgrades of the base container and can be mounted into different flavors of KasmVNC based containers on the fly. This can be achieved from the command line with:
proot-apps install filezilla
PRoot Apps is included in all KasmVNC based containers, a list of linuxserver.io supported applications is located HERE.
It is possible to install extra packages during container start using universal-package-install. It might increase starting time significantly. PRoot is preferred.
environment:
- DOCKER_MODS=linuxserver/mods:universal-package-install
- INSTALL_PACKAGES=libfuse2|git|gdb
This container is capable of delivering a true lossless image at a high framerate to your web browser by changing the Stream Quality preset to "Lossless", more information here. In order to use this mode from a non localhost endpoint the HTTPS port on 3001 needs to be used. If using a reverse proxy to port 3000 specific headers will need to be set as outlined here.
To help you get started creating a container from this image you can either use docker-compose or the docker cli.
docker-compose (recommended, click here for more info)
---
services:
chromium:
image: lscr.io/linuxserver/chromium:latest
container_name: chromium
security_opt:
- seccomp:unconfined #optional
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- CHROME_CLI=https://www.linuxserver.io/ #optional
volumes:
- /path/to/config:/config
ports:
- 3000:3000
- 3001:3001
shm_size: "1gb"
restart: unless-stopped
docker cli (click here for more info)
docker run -d \
--name=chromium \
--security-opt seccomp=unconfined `#optional` \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Etc/UTC \
-e CHROME_CLI=https://www.linuxserver.io/ `#optional` \
-p 3000:3000 \
-p 3001:3001 \
-v /path/to/config:/config \
--shm-size="1gb" \
--restart unless-stopped \
lscr.io/linuxserver/chromium:latest
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.
| Parameter | Function |
|---|---|
| 3000 | Chromium desktop gui. |
| 3001 | HTTPS Chromium desktop gui. |
- Env: PUID=1000
- Function: for UserID - see below for explanation
- Env: PGID=1000
- Function: for GroupID - see below for explanation
- Env: TZ=Etc/UTC
- Function: specify a timezone to use, see this list.
- Env: CHROME_CLI=https://www.linuxserver.io/
- Function: Specify one or multiple Chromium CLI flags, this string will be passed to the application in full.
| Volume | Function |
|---|---|
| /config | Users home directory in the container, stores local files and settings |
- Parameter: --shm-size=
- Function: This is needed for any modern website to function like youtube.
- Parameter: --security-opt seccomp=unconfined
- Function: For Docker Engine only, many modern gui apps need this to function on older hosts as syscalls are unknown to Docker. Chromium runs in no-sandbox test mode without it.
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.
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.
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:
Example output:
uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)
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.
-
Shell access whilst the container is running:
docker exec -it chromium /bin/bash
* To monitor the logs of the container in realtime:
* Container version number:
```
docker inspect -f '{{ index .Config.Labels "build_version" }}' chromium
-
Image version number:
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/chromium:latest
Updating Info
-------------------------------------------------
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the [Application Setup](#application-setup) section above to see if it is recommended for the image.
Below are the instructions for updating containers:
### Via Docker Compose
* Update images:
* All images:
* Single image:
```
docker-compose pull chromium
-
Update containers:
-
All containers:
-
Single container:
-
docker-compose up -d chromium
* You can also remove the old dangling images:
### Via Docker Run
* Update the image:
```
docker pull lscr.io/linuxserver/chromium:latest
-
Stop the running container:
-
Delete the container:
-
Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your
/configfolder and settings will be preserved) -
You can also remove the old dangling images:
Tip
We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-chromium.git
cd docker-chromium
docker build \
--no-cache \
--pull \
-t lscr.io/linuxserver/chromium: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.
- 10.02.24: - Update Readme with new env vars and ingest proper PWA icon.
- 08.01.24: - Fix re-launch issue for chromium by purging temp files on launch.
- 29.12.23: - Rebase to Debian Bookworm.
- 13.05.23: - Rebase to Alpine 3.18.
- 01.04.23: - Preserve arguments passed to Chromium and restructure to use wrapper.
- 18.03.23: - Initial release.
Forked and Edited by: GitXpresso
Original Repository: Docker Tor Browser
Configuration
Others
Tor browser running inside of Firefox
This image allows running a Tor browser instance on any headless server. The browser can be accessed via either a web interface or directly from any VNC client.
Container is based on baseimage-gui by jlesage
Both amd64 and arm64 container runtimes are supported, but only the amd64 image uses an official build of the Tor Browser. The arm64 image uses an unofficial build via tor-browser-ports because the Tor Project does not have an official arm build of the Tor Browser. Both the official and unofficial builds are signed, and the signatures are verified when building this container.
See the docker-compose here or use this command
docker run -d -p 5800:5800 domistyle/tor-browser
The web interface will be available on port 5800. to use port on a browser go to this url
127.0.0.1:8080
No special configuration is necessary, however some recommended variables are available:
| Variable | Description | Default | Required |
|---|---|---|---|
DISPLAY_WIDTH |
Set the width of the virtual screen | 1280 |
No |
DISPLAY_HEIGHT |
Set the height of the virtual screen | 768 |
No |
KEEP_APP_RUNNING |
Automatically restarts the Tor browser if it exits | 0 |
No |
TZ |
Set the time zone for the container | - | No |
** For advanced configuration options please take a look here.**
You may install the browser with your own configuration. Copy the template configuration to get started.
If mozilla.cfg is available then it is used, otherwise no browser changes are made.
cd browser-cfg
cp mozilla.cfg.template mozilla.cfg
** For more information on the available options: http://kb.mozillazine.org/About:config_entries
It is not recommended to add persistent volumes to your Tor Browser. We do not support any issues that arise from persistent volumes.
version: '3.9'
services:
tor:
image: domistyle/tor-browser
container_name: tor
restart: unless-stopped
ports:
- 5800:5800
- 5900:5900
environment:
DISPLAY_WIDTH: 1920
DISPLAY_HEIGHT: 1080
KEEP_APP_RUNNING: 1
TZ: Europe/ViennaTo install tor browser using docker compose, copy and paste the command in your terminal
docker compose upTo stop the docker container do
docker stop torTo start the container again, put the following command below and paste it in your terminal
docker start torTo remove the container you can do
docker compose downor you can do this
docker rm tor
First update all your packages by doing
sudo apt updateAfter you update all your packages then it is time to install docker.io by doing
sudo apt install -y docker.ioTo add systemctl to docker do this
sudo systemctl enable docker --nowTo verify that you docker put the following command below
dockerTo use docker without doing sudo every time do this
sudo usermod -aG docker $USER| Port | Description |
|---|---|
5800 |
Provides a web interface to access the Tor browser |
5900 |
Provides direct access to the NoVNC server |
- shm_size might need to be set to 2GB or more if you experience crashes
Docker
- [Docker Compose Script](#Docker-Compose-Script) - [Docker Container Commands](#Docker-Container-Commands) - [Docker Installation](#How-to-install-Docker)Configuration
Others
Tor browser running inside of Firefox
This image allows running a Tor browser instance on any headless server. The browser can be accessed via either a web interface or directly from any VNC client.
Container is based on baseimage-gui by jlesage
Both amd64 and arm64 container runtimes are supported, but only the amd64 image uses an official build of the Tor Browser. The arm64 image uses an unofficial build via tor-browser-ports because the Tor Project does not have an official arm build of the Tor Browser. Both the official and unofficial builds are signed, and the signatures are verified when building this container.
See the docker-compose here to use this command as a faster way of installing Tor.
docker run -d -p 5800:5800 --name tor domistyle/tor-browser --restart=unless-stopped
The web interface will be available on port 5800.
No special configuration is necessary, however some recommended variables are available:
| Variable | Description | Default | Required |
|---|---|---|---|
DISPLAY_WIDTH |
Set the width of the virtual screen | 1280 |
No |
DISPLAY_HEIGHT |
Set the height of the virtual screen | 768 |
No |
KEEP_APP_RUNNING |
Automatically restarts the Tor browser if it exits | 0 |
No |
TZ |
Set the time zone for the container | - | No |
** For advanced configuration options please take a look here.**
You may install the browser with your own configuration. Copy the template configuration to get started.
If mozilla.cfg is available then it is used, otherwise no browser changes are made.
cd browser-cfg
cp mozilla.cfg.template mozilla.cfg
** For more information on the available options: http://kb.mozillazine.org/About:config_entries
It is not recommended to add persistent volumes to your Tor Browser. We do not support any issues that arise from persistent volumes.
version: '3.9'
services:
tor:
image: domistyle/tor-browser
container_name: tor
restart: unless-stopped
ports:
- 5800:5800
- 5900:5900
environment:
DISPLAY_WIDTH: 1920
DISPLAY_HEIGHT: 1080
KEEP_APP_RUNNING: 1
TZ: Europe/ViennaTo install tor browser using docker compose, copy and paste the command in your terminal
docker compose upTo stop the docker container do
docker stop torTo start the container again, put the following command below and paste it in your terminal
docker start torTo remove the container you can do
docker compose downor you can do this
docker rm tor
First update all your packages by doing
sudo apt updateAfter you update all your packages then it is time to install docker.io by doing
sudo apt install -y docker.ioTo add systemctl to docker do this
sudo systemctl enable docker --nowTo verify that you docker put the following command below
dockerTo use docker without doing sudo every time do this
sudo usermod -aG docker $USER| Port | Description |
|---|---|
5800 |
Provides a web interface to access the Tor browser |
5900 |
Provides direct access to the NoVNC server |
| IP | Description |
127.0.0.1 |
Provides a way to use tor on your browser |
- shm_size might need to be set to 2GB or more if you experience crashes
Repository: Gogs
User: Gogs
Donate:
The Gogs (/gɑgz/) project aims to build a simple, stable and extensible self-hosted Git service that can be set up in the most painless way. With Go, this can be done with an independent binary distribution across all platforms that Go supports, including Linux, macOS, Windows and ARM-based systems.
- Please visit our home page for user documentation.
- Please refer to CHANGELOG.md for list of changes in each releases.
- Want to try it before doing anything else? Do it online!
- Having trouble? Help yourself with troubleshooting or ask questions in Discussions.
- Want to help with localization? Check out the localization documentation.
- Ready to get hands dirty? Read our contributing guide.
- Hmm... What about APIs? We have experimental support with documentation.
- User dashboard, user profile and activity timeline.
- Access repositories via SSH, HTTP and HTTPS protocols.
- User, organization and repository management.
- Repository and organization webhooks, including Slack, Discord and Dingtalk.
- Repository Git hooks, deploy keys and Git LFS.
- Repository issues, pull requests, wiki, protected branches and collaboration.
- Migrate and mirror repositories with wiki from other code hosts.
- Web editor for quick editing repository files and wiki.
- Jupyter Notebook and PDF rendering.
- Authentication via SMTP, LDAP, reverse proxy, GitHub.com and GitHub Enterprise with 2FA.
- Customize HTML templates, static files and many others.
- Rich database backend, including PostgreSQL, MySQL, SQLite3 and TiDB.
- Have localization over 31 languages.
- A Raspberry Pi or $5 Digital Ocean Droplet is more than enough to get you started. Some even use 64MB RAM Docker CaaS.
- 2 CPU cores and 512MB RAM would be the baseline for teamwork.
- Increase CPU cores when your team size gets significantly larger, memory footprint remains low.
- Please see Semantic UI for specific versions of supported browsers.
- The smallest resolution officially supported is 1024*768, however the UI may still look right in smaller resolutions, but no promises or fixes.
Visit Docker Hub or GitHub Container registry to see all available images and tags.
To keep your data out of Docker container, we do a volume (/var/gogs -> /data) here, and you can change it based on your situation.
# Pull image from Docker Hub.
docker pull gogs/gogs
# Create local directory for volume.
mkdir -p /var/gogs
# Use `docker run` for the first time.
docker run --name=gogs -p 10022:22 -p 10880:3000 -v /var/gogs:/data gogs/gogs
# Use `docker start` if you have stopped it.
docker start gogsNote: It is important to map the SSH service from the container to the host and set the appropriate SSH Port and URI settings when setting up Gogs for the first time. To access and clone Git repositories with the above configuration you would use: git clone ssh://git@hostname:10022/username/myrepo.git for example.
Files will be store in local path /var/gogs in my case.
Directory /var/gogs keeps Git repositories and Gogs data:
/var/gogs
|-- git
| |-- gogs-repositories
|-- ssh
| |-- # ssh public/private keys for Gogs
|-- gogs
|-- conf
|-- data
|-- log
The "custom" directory may not be obvious in Docker environment. The /var/gogs/gogs (in the host) and /data/gogs (in the container) is already the "custom" directory and you do not need to create another layer but directly edit corresponding files under this directory.
# Create docker volume.
$ docker volume create --name gogs-data
# Use `docker run` for the first time.
$ docker run --name=gogs -p 10022:22 -p 10880:3000 -v gogs-data:/data gogs/gogsMost of the settings are obvious and easy to understand, but there are some settings can be confusing by running Gogs inside Docker:
- Repository Root Path: keep it as default value
/home/git/gogs-repositoriesbecausestart.shalready made a symbolic link for you. - Run User: keep it as default value
gitbecausebuild/finalize.shalready setup a user with namegit. - Domain: fill in with Docker container IP (e.g.
192.168.99.100). But if you want to access your Gogs instance from a different physical machine, please fill in with the hostname or IP address of the Docker host machine. - SSH Port: Use the exposed port from Docker container. For example, your SSH server listens on
22inside Docker, but you expose it by10022:22, then use10022for this value. Builtin SSH server is not recommended inside Docker Container - HTTP Port: Use port you want Gogs to listen on inside Docker container. For example, your Gogs listens on
3000inside Docker, and you expose it by10880:3000, but you still use3000for this value. - Application URL: Use combination of Domain and exposed HTTP Port values (e.g.
http://192.168.99.100:10880/).
Full documentation of application settings can be found here.
This container has some options available via environment variables, these options are opt-in features that can help the administration of this container:
- SOCAT_LINK:
- Possible value:
true,false,1,0 - Default:
true - Action: Bind linked docker container to localhost socket using socat. Any exported port from a linked container will be binded to the matching port on localhost.
- Disclaimer:
As this option rely on the environment variable created by docker when a container is linked, this option should be deactivated in managed environment such as Rancher or Kubernetes (set to
0orfalse)
- Possible value:
- RUN_CROND:
- Possible value:
true,false,1,0 - Default:
false - Action:
Request crond to be run inside the container. Its default configuration will periodically run all scripts from
/etc/periodic/${period}but custom crontabs can be added to/var/spool/cron/crontabs/.
- Possible value:
- BACKUP_INTERVAL:
- Possible value:
3h,7d,3M - Default:
null - Action:
In combination with
RUN_CRONDset totrue, enables backup system.
See: Backup System
- Possible value:
- BACKUP_RETENTION:
- Possible value:
360m,7d,...m/d - Default:
7d - Action:
Used by backup system. Backups older than specified in expression are deleted periodically.
See: Backup System
- Possible value:
- BACKUP_ARG_CONFIG:
- Possible value:
/app/gogs/example/custom/config - Default:
null - Action:
Used by backup system. If defined, supplies
--configargument togogs backup.
See: Backup System
- Possible value:
- BACKUP_ARG_EXCLUDE_REPOS:
- Possible value:
test-repo1,test-repo2 - Default:
null - Action:
Used by backup system. If defined, supplies
--exclude-reposargument togogs backup.
See: Backup System
- Possible value:
- BACKUP_EXTRA_ARGS:
- Possible value:
--verbose --exclude-mirror-repos - Default:
null - Action:
Used by backup system. If defined, append content to arguments to
gogs backup.
See: Backup System
- Possible value:
Automated backups with retention policy:
BACKUP_INTERVALcontrols how often the backup job runs and supports interval in hours (h), days (d), and months (M), eg.3h,7d,3M. The lowest possible value is one hour (1h).BACKUP_RETENTIONsupports expressions in minutes (m) and days (d), eg.360m,2d. The lowest possible value is 60 minutes (60m).
❗❗❗Make sure you have volumed data to somewhere outside Docker container❗❗❗
Steps to upgrade Gogs with Docker:
docker pull gogs/gogsdocker stop gogsdocker rm gogs- Finally, create a container for the first time and don't forget to do the same for the volume and port mapping.
- The docker container cannot currently be built on Raspberry 1 (armv6l) as our base image
alpinedoes not have agopackage available for this platform.
Make the file executable
chmod u+x dockerkali.shRun the bash file
./dockerkali.shMake the file executable
chmod u+x composekali.shRun the bash file
./composekali.shTo install and run the container do
docker compose up
To restart the container do
docker compose restart
To remove the container do
docker compose down
Moving to the current directory that you are in to the "Shell" directory
cd ShellMake the file executable
chmod u+x ./gogs.shStarting gogs.sh
./gogs.shMoving to the current directory that you are in to the "Shell" directory
cd ShellMake the file executable
chmod u+x ./go.sh
Run the bash file
./go.sh
Move from CLODSH to CLODSH/Shell
cd ShellMake the file executable
chmod u+x ./rmgo.shUninstalling Go
./rmgo.shVersion: 1.38