Whoogle

Name: Whoogle
Author: benbusby

Container

Other Tools

Self-hosted, ad-free, privacy-respecting Google metasearch engine.

Image details

Pulls: 20.2M

Architecture: amd64, arm64, arm/v7

Image size: 55 MB

Latest: 1.2.4

User: benbusby

Created: May 10, 2020

Updated: 4 months ago

Status: active

Source details

Repo: benbusby/whoogle-search

Stars: 11.6k

Forks: 1k

Language: Python

License: MIT

Latest: v1.2.4 · 4 months ago

Updated: 1 day ago

Website: pypi.org/project/whoogle-search/

Status: archived

Configuration

Type

Container

Platform

linux

Image

benbusby/whoogle-search:latest

Ports

5001:5000/tcp

Volumes

/config : /portainer/Files/AppData/Config/Whoogle

Restart

unless-stopped

Template by novaspirit

Notes

Template created by Pi-Hosted Series
Check our Github page: https://github.com/pi-hosted/pi-hosted

Official Webpage: https://github.com/benbusby/whoogle-search
Official Docker Documentation: https://github.com/benbusby/whoogle-search#g-manual-docker

Pre-installation script must be RAN before you install: wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/tools/install_whoogle.sh | bash

Youtube Video: Novaspirit Tech - How to Install Whoogle to replace using Google and repo notes

Standalone Install

Select an install method, to see config/commands for deploying Whoogle

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

Ensure both Docker and Portainer are installed, and up-to-date
Log into your Portainer web UI
Under Settings → App Templates, paste the below URL
Head to Home → App Templates, and the list of apps will show up
Select Whoogle, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json

Show Me

More install options in our documentation, or see benbusby/whoogle-search for app-specific guidance.

Get Google search results, but without any ads, javascript, AMP links, cookies, or IP address tracking. Easily deployable in one click as a Docker app, and customizable with a single config file. Quick and simple to implement as a primary search engine replacement on both desktop and mobile.
Contents

Features
Dependencies
Install/Deploy

1. [Heroku Quick Deploy](#a-heroku-quick-deploy)
2. [Repl.it](#b-replit)
3. [Fly.io](#c-flyio)
4. [pipx](#d-pipx)
5. [pip](#e-pip)
6. [Manual](#f-manual)
7. [Docker](#g-manual-docker)
8. [Arch/AUR](#arch-linux--arch-based-distributions)

Environment Variables and Configuration
Usage
Extra Steps

1. [Set Primary Search Engine](#set-whoogle-as-your-primary-search-engine)
2. [Prevent Downtime (Heroku Only)](#prevent-downtime-heroku-only)
3. [Manual HTTPS Enforcement](#https-enforcement)
4. [Using with Firefox Containers](#using-with-firefox-containers)

Contributing
FAQ
Public Instances
Screenshots
Mirrors (read-only)

1. [GitLab](https://gitlab.com/benbusby/whoogle-search)
2. [Gogs](https://gogs.benbusby.com/benbusby/whoogle-search)

Features

No ads or sponsored content
No javascript
No cookies
No tracking/linking of your personal IP address\*
No AMP links
No URL tracking tags (i.e. utm=%s)
No referrer header
Tor and HTTP/SOCKS proxy support
Autocomplete/search suggestions
POST request search and suggestion queries (when possible)
View images at full res without site redirect (currently mobile only)
Dark mode
Randomly generated User Agent
Easy to install/deploy
DDG-style bang (i.e. !<tag> <query>) searches
Optional location-based searching (i.e. results near \)
Optional NoJS mode to disable all Javascript in results

^{If deployed to a remote server, or configured to send requests through a VPN, Tor, proxy, etc.}

Dependencies

If using Heroku Quick Deploy, you can skip this section.
Docker (Windows, macOS, Ubuntu, other Linux distros)
- Only needed if you intend on deploying the app as a Docker image
Python3
libcurl4-openssl-dev and libssl-dev
- macOS: brew install openssl curl-openssl - Ubuntu: sudo apt-get install -y libcurl4-openssl-dev libssl-dev - Arch: pacman -S curl openssl
Install
There are a few different ways to begin using the app, depending on your preferences:
A) Heroku Quick Deploy

Note: Requires a (free) Heroku account
Provides:

Free deployment of app
Free HTTPS url (https://\.herokuapp.com)
Downtime after periods of inactivity \(solution\)

B) Repl.it

Note: Requires a (free) Replit account
Provides:

Free deployment of app
Free HTTPS url (https://\.\\.repl\.co)

- Supports custom domains

Downtime after periods of inactivity \(solution 1, solution 2\)

C) Fly.io

You will need a Fly.io account to do this. Fly requires a credit card to deploy anything, but you can have up to 3 shared-CPU VMs running full-time each month for free.

Install the CLI:

curl -L https://fly.io/install.sh | sh

Deploy your app

fly apps create --org personal --port 5000
# Choose a name and the Image builder
# Enter `benbusby/whoogle-search:latest` as the image name
fly deploy

Your app is now available at https://<app-name>.fly.dev.
You can customize the fly.toml:

Remove the non-https service
Add environment variables under the [env] key

- Use fly secrets set NAME=value for more sensitive values like WHOOGLE_PASS and WHOOGLE_PROXY_PASS.

D) pipx

Persistent install:
pipx install git+https://github.com/benbusby/whoogle-search.git
Sandboxed temporary instance:
pipx run --spec git+https://github.com/benbusby/whoogle-search.git whoogle-search

E) pip

pip install whoogle-search

$ whoogle-search --help
usage: whoogle-search [-h] [--port <port number>] [--host <ip address>] [--debug] [--https-only] [--userpass <username:password>]
                      [--proxyauth <username:password>] [--proxytype <socks4|socks5|http>] [--proxyloc <location:port>]

Whoogle Search console runner

optional arguments:
  -h, --help            Show this help message and exit
  --port <port number>  Specifies a port to run on (default 5000)
  --host <ip address>   Specifies the host address to use (default 127.0.0.1)
  --debug               Activates debug mode for the server (default False)
  --https-only          Enforces HTTPS redirects for all requests
  --userpass <username:password>
                        Sets a username/password basic auth combo (default None)
  --proxyauth <username:password>
                        Sets a username/password for a HTTP/SOCKS proxy (default None)
  --proxytype <socks4|socks5|http>
                        Sets a proxy type for all connections (default None)
  --proxyloc <location:port>
                        Sets a proxy location for all connections (default None)

See the available environment variables for additional configuration.

F) Manual

Note: Content-Security-Policy headers are already sent by Whoogle -- you don't/shouldn't need to apply a CSP header yourself
Clone the repo and run the following commands to start the app in a local-only environment:

git clone https://github.com/benbusby/whoogle-search.git
cd whoogle-search
python3 -m venv venv
source venv/bin/activate
pip install -r requirements.txt
./run

See the available environment variables for additional configuration.

systemd Configuration

After building the virtual environment, you can add the following to /lib/systemd/system/whoogle.service to set up a Whoogle Search systemd service:

[Unit]
Description=Whoogle

[Service]
# Basic auth configuration, uncomment to enable
#Environment=WHOOGLE_USER=<username>
#Environment=WHOOGLE_PASS=<password>
# Proxy configuration, uncomment to enable
#Environment=WHOOGLE_PROXY_USER=<proxy username>
#Environment=WHOOGLE_PROXY_PASS=<proxy password>
#Environment=WHOOGLE_PROXY_TYPE=<proxy type (http|https|proxy4|proxy5)
#Environment=WHOOGLE_PROXY_LOC=<proxy host/ip>
# Site alternative configurations, uncomment to enable
# Note: If not set, the feature will still be available
# with default values. 
#Environment=WHOOGLE_ALT_TW=nitter.net
#Environment=WHOOGLE_ALT_YT=invidious.snopyta.org
#Environment=WHOOGLE_ALT_IG=bibliogram.art/u
#Environment=WHOOGLE_ALT_RD=libredd.it
#Environment=WHOOGLE_ALT_TL=lingva.ml
# Load values from dotenv only
#Environment=WHOOGLE_DOTENV=1
Type=simple
User=root
WorkingDirectory=<whoogle_directory>
ExecStart=<whoogle_directory>/venv/bin/python3 -um app --host 0.0.0.0 --port 5000
ExecReload=/bin/kill -HUP $MAINPID
Restart=always
RestartSec=3
SyslogIdentifier=whoogle

[Install]
WantedBy=multi-user.target

Then,

sudo systemctl daemon-reload
sudo systemctl enable whoogle
sudo systemctl start whoogle

G) Manual (Docker)

Ensure the Docker daemon is running, and is accessible by your user account

- To add user permissions, you can execute sudo usermod -aG docker yourusername - Running docker ps should return something besides an error. If you encounter an error saying the daemon isn't running, try sudo systemctl start docker (Linux) or ensure the docker tool is running (Windows/macOS).

Clone and deploy the docker app using a method below:

Docker CLI

Note: For ARM machines, use the buildx-experimental Docker tag.
Through Docker Hub:
docker pull benbusby/whoogle-search docker run --publish 5000:5000 --detach --name whoogle-search benbusby/whoogle-search:latest

or with docker-compose:
git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search docker-compose up

or by building yourself:
git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search docker build --tag whoogle-search:1.0 . docker run --publish 5000:5000 --detach --name whoogle-search whoogle-search:1.0

Optionally, you can also enable some of the following environment variables to further customize your instance:
docker run --publish 5000:5000 --detach --name whoogle-search \ -e WHOOGLE_USER=username \ -e WHOOGLE_PASS=password \ -e WHOOGLE_PROXY_USER=username \ -e WHOOGLE_PROXY_PASS=password \ -e WHOOGLE_PROXY_TYPE=socks5 \ -e WHOOGLE_PROXY_LOC=ip \ whoogle-search:1.0

And kill with: docker rm --force whoogle-search
Using Heroku CLI
heroku login heroku container:login git clone https://github.com/benbusby/whoogle-search.git cd whoogle-search heroku create heroku container:push web heroku container:release web heroku open

This series of commands can take a while, but once you run it once, you shouldn't have to run it again. The final command, heroku open will launch a tab in your web browser, where you can test out Whoogle and even set it as your primary search engine. You may also edit environment variables from your app’s Settings tab in the Heroku Dashboard.

Arch Linux & Arch-based Distributions

There is an AUR package available, as well as a pre-built and daily updated package available at Chaotic-AUR.

Using your own server, or alternative container deployment

There are other methods for deploying docker containers that are well outlined in this article, but there are too many to describe set up for each here. Generally it should be about the same amount of effort as the Heroku deployment.
Depending on your preferences, you can also deploy the app yourself on your own infrastructure. This route would require a few extra steps: - A server (I personally recommend Digital Ocean or Linode, their cheapest tiers will work fine) - Your own URL (I suppose this is optional, but recommended) - SSL certificates (free through Let's Encrypt) - A bit more experience or willingness to work through issues

Environment Variables

There are a few optional environment variables available for customizing a Whoogle instance. These can be set manually, or copied into whoogle.env and enabled for your preferred deployment method:

Local runs: Set WHOOGLE_DOTENV=1 before running
With docker-compose: Uncomment the env_file option
With docker build/run: Add --env-file ./whoogle.env to your command

Variable	Description
WHOOGLEDOTENV	Load environment variables in `whoogle.env`
WHOOGLEUSER	The username for basic auth. WHOOGLEPASS must also be set if used.
WHOOGLEPASS	The password for basic auth. WHOOGLEUSER must also be set if used.
WHOOGLEPROXYUSER	The username of the proxy server.
WHOOGLEPROXYPASS	The password of the proxy server.
WHOOGLEPROXYTYPE	The type of the proxy server. Can be "socks5", "socks4", or "http".
WHOOGLEPROXYLOC	The location of the proxy server (host or ip).
EXPOSEPORT	The port where Whoogle will be exposed.
HTTPSONLY	Enforce HTTPS. (See here)
WHOOGLEALTTW	The twitter.com alternative to use when site alternatives are enabled in the config.
WHOOGLEALTYT	The youtube.com alternative to use when site alternatives are enabled in the config.
WHOOGLEALTIG	The instagram.com alternative to use when site alternatives are enabled in the config.
WHOOGLEALTRD	The reddit.com alternative to use when site alternatives are enabled in the config.
WHOOGLEALTTL	The Google Translate alternative to use. This is used for all "translate " searches.

Config Environment Variables

These environment variables allow setting default config values, but can be overwritten manually by using the home page config menu. These allow a shortcut for destroying/rebuilding an instance to the same config state every time.

Variable	Description
WHOOGLECONFIGDISABLE	Hide config from UI and disallow changes to config by client
WHOOGLECONFIGCOUNTRY	Filter results by hosting country
WHOOGLECONFIGLANGUAGE	Set interface language
WHOOGLECONFIGSEARCHLANGUAGE	Set search result language
WHOOGLECONFIGBLOCK	Block websites from search results (use comma-separated list)
WHOOGLECONFIGTHEME	Set theme mode (light, dark, or system)
WHOOGLECONFIGSAFE	Enable safe searches
WHOOGLECONFIGALTS	Use social media site alternatives (nitter, invidious, etc)
WHOOGLECONFIGTOR	Use Tor routing (if available)
WHOOGLECONFIGNEWTAB	Always open results in new tab
WHOOGLECONFIGVIEWIMAGE	Enable View Image option
WHOOGLECONFIGGETONLY	Search using GET requests only
WHOOGLECONFIGURL	The root url of the instance (`https://<your url>/`)
WHOOGLECONFIGSTYLE	The custom CSS to use for styling (should be single line)

Usage

Same as most search engines, with the exception of filtering by time range.
To filter by a range of time, append ":past " to the end of your search, where can be hour, day, month, or year. Example: coronavirus updates :past hour

Extra Steps

Set Whoogle as your primary search engine

Note: If you're using a reverse proxy to run Whoogle Search, make sure the "Root URL" config option on the home page is set to your URL before going through these steps.
Browser settings: - Firefox (Desktop)

- Version 89+
  - Navigate to your app's url, right click the address bar, and select "Add Search Engine".
- Previous versions
  - Navigate to your app's url, and click the 3 dot menu in the address bar. At the bottom, there should be an option to "Add Search Engine".
- Once you've added the new search engine, open your Firefox Preferences menu, click "Search" in the left menu, and use the available dropdown to select "Whoogle" from the list.
- **Note**: If your Whoogle instance uses Firefox Containers, you'll need to [go through the steps here](#using-with-firefox-containers) to get it working properly.

- Firefox (iOS)

- In the mobile app Settings page, tap "Search" within the "General" section. There should be an option titled "Add Search Engine" to select. It should prompt you to enter a title and search query url - use the following elements to fill out the form:
  - Title: "Whoogle"
  - URL: `http[s]://\<your whoogle url\>/search?q=%s`

- Firefox (Android)

- Version <79.0.0
  - Navigate to your app's url
  - Long-press on the search text field
  - Click the "Add Search Engine" menu item
    - Select a name and click ok
  - Click the 3 dot menu in the top right
  - Navigate to the settings menu and select the "Search" sub-menu
  - Select Whoogle and press "Set as default"
- Version >=79.0.0
  - Click the 3 dot menu in the top right
  - Navigate to the settings menu and select the "Search" sub-menu
  - Click "Add search engine"
  - Select the 'Other' radio button
    - Name: "Whoogle"
    - Search string to use: `https://\<your whoogle url\>/search?q=%s`

- Alfred (Mac OS X)

1. Go to `Alfred Preferences` > `Features` > `Web Search` and click `Add Custom Search`. Then configure these settings
		   - Search URL: `https://\<your whoogle url\>/search?q={query}
		   - Title: `Whoogle for '{query}'` (or whatever you want)
		   - Keyword: `whoogle`

2. Go to `Default Results` and click the `Setup fallback results` button. Click `+` and add Whoogle, then  drag it to the top.

- Chrome/Chromium-based Browsers

- Automatic
  - Visit the home page of your Whoogle Search instance -- this may automatically add the search engine to your list of search engines. If not, you can add it manually.
- Manual
  - Under search engines > manage search engines > add, manually enter your Whoogle instance details with a `<whoogle url>/search?q=%s` formatted search URL.

Prevent Downtime (Heroku only)

Part of the deal with Heroku's free tier is that you're allocated 550 hours/month (meaning it can't stay active 24/7), and the app is temporarily shut down after 30 minutes of inactivity. Once it becomes inactive, any Whoogle searches will still work, but it'll take an extra 10-15 seconds for the app to come back online before displaying the result, which can be frustrating if you're in a hurry.
A good solution for this is to set up a simple cronjob on any device at your home that is consistently powered on and connected to the internet (in my case, a PiHole worked perfectly). All the device needs to do is fetch app content on a consistent basis to keep the app alive in whatever ~17 hour window you want it on (17 hrs 31 days = 527, meaning you'd still have 23 leftover hours each month if you searched outside of your target window).
For instance, adding */20 7-23 * * * curl https://<your heroku app name>.herokuapp.com > /home/<username>/whoogle-refresh will fetch the home page of the app every 20 minutes between 7am and midnight, allowing for downtime from midnight to 7am. And again, this wouldn't be a hard limit - you'd still have plenty of remaining hours of uptime each month in case you were searching after this window has closed.
Since the instance is destroyed and rebuilt after inactivity, config settings will be reset once the app enters downtime. If you have configuration settings active that you'd like to keep between periods of downtime (like dark mode for example), you could instead add */20 7-23 * * * curl -d "dark=1" -X POST https://<your heroku app name>.herokuapp.com/config > /home/<username>/whoogle-refresh to keep these settings more or less permanent, and still keep the app from entering downtime when you're using it.
HTTPS Enforcement
Only needed if your setup requires Flask to redirect to HTTPS on its own -- generally this is something that doesn't need to be handled by Whoogle Search.
Note: You should have your own domain name and an https certificate in order for this to work properly.

Heroku: Ensure that the Root URL configuration on the home page begins with https:// and not http://
Docker build: Add --build-arg use_https=1 to your run command
Docker image: Set the environment variable HTTPSONLY=1
Pip/Pipx: Add the --https-only flag to the end of the whoogle-search command
Default run script: Modify the script locally to include the --https-only flag at the end of the python run command

Using with Firefox Containers

Unfortunately, Firefox Containers do not currently pass through POST requests (the default) to the engine, and Firefox caches the opensearch template on initial page load. To get around this, you can take the following steps to get it working as expected:

Remove any existing Whoogle search engines from Firefox settings
Enable GET Requests Only in Whoogle config
Clear Firefox cache
Restart Firefox
Navigate to Whoogle instance and re-add the engine

Serve Whoogle on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxy Domain App port Upstream

Proxying whoogle.example.com to http://whoogle:5000

Add this to your Caddyfile

whoogle.example.com {
	reverse_proxy http://whoogle:5000
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

In Portainer, go to Containers, click the container, then Logs. Or run docker logs whoogle
Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5001 failed: port is already allocated", something else on your server is using that port.

Find what's using it: sudo ss -tlnp | grep :5001
Stop the other service, or pick a different host port. In 5001:5000 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

Use your server's real IP: http://your-server-ip:5001. The 0.0.0.0 link Portainer shows isn't a real address.
Give it a minute after first deploy, whoogle can take a while to initialise.
Make sure your firewall allows the port, e.g. sudo ufw allow 5001

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/Whoogle

Image won't pull

Test the pull directly on the host: docker pull benbusby/whoogle-search:latest

"manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
"toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
"no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

This image supports: amd64, arm64, arm/v7
Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

Check the logs right after a restart, the last few lines before it died are the useful ones.
Get the exit code with docker inspect whoogle --format '{{.State.ExitCode}}'
Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Upstream project is archived

The developers have archived benbusby/whoogle-search, so bugs and security issues won't be fixed.

It'll keep working for now, but consider the similar apps below for a maintained alternative.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

Bug within the app: Open an issue on benbusby/whoogle-search
Template not working: Open an issue on novaspirit/pi-hosted
This website not working: Open an issue on lissy93/portainer-templates

A single container

Whoogle runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Whoogle needs bundled into one download. This template pulls benbusby/whoogle-search:latest, which Docker fetches once (about 55 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Whoogle's comes from Docker Hub, published by benbusby.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 1.2.4. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 5001:5000 means it's reachable on port 5001 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

5001:5000

Volumes

A volume is where Whoogle keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

/config from /portainer/Files/AppData/Config/Whoogle on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Whoogle after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Nothing custom is set, so Whoogle sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container whoogle. That's what you'll spot in the containers list and use in commands like docker logs whoogle.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Whoogle is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Whoogle up. Add the template list to Portainer once, then deploying Whoogle is a click rather than a wall of config.

Whoogle

Image details

Source details

Configuration

Notes

Pre-installation script must be RAN before you install: wget -qO- https://raw.githubusercontent.com/pi-hosted/pi-hosted/master/tools/install_whoogle.sh | bash

Standalone Install

Install on Portainer

Template Import URL

Container Documentation

Features

Dependencies

Install

A) Heroku Quick Deploy

B) Repl.it

C) Fly.io

Install the CLI:

Deploy your app

D) pipx

E) pip

F) Manual

systemd Configuration

G) Manual (Docker)

Docker CLI

Using Heroku CLI

Arch Linux & Arch-based Distributions

Using your own server, or alternative container deployment

Environment Variables

Config Environment Variables

Usage

Extra Steps

Set Whoogle as your primary search engine

Prevent Downtime (Heroku only)

HTTPS Enforcement

Using with Firefox Containers

Recent versions

Proxy configurator

Troubleshooting

Check the logs first

Port already in use

Running but the page won't load

Permission denied on volumes

Image won't pull

"exec format error"

Container keeps restarting

Upstream project is archived

Raise an issue

Config glossary

A single container

The app image

Where the image comes from

Version tags

Which machines it runs on

Ports

Volumes

Restart policy

Networking

Container name

Platform

Open source license

Portainer app templates

Similar apps