Docker app installer

install_redis705_base_docker.sh

Creates /data/redis7.0.5, writes redis.conf only if absent, pulls redis:7.0.5 and replaces a same-name container. Existing config and data are reused; a new password input does not update an existing requirepass.

One-liner

curl -fL 'https://www.helper.sh/install_redis705_base_docker.sh' -o './install_redis705_base_docker.sh'

This command downloads the bundled file only; it does not run it. Inspect the saved source and compare its version before deciding whether to execute it.

Raw file

Download script for review Raw script

Bundled in this site

Check the file you downloaded

Compare a saved file with the exact bytes bundled in this page’s build. The file stays in this tab; this tool does not upload or persist it. Maximum 2 MiB.

Expected SHA-256
1dff99da3bc7da24e7e14dace74a716a9be1592b77ce03a42864065022bf391b

Bundled byte count: 4562

Save checksum file

Save the script and checksum in the same directory. On Linux with GNU Coreutils, the command below checks the saved bytes only; it does not run the script. Keep the original filename for this command.

sha256sum --check './install_redis705_base_docker.sh.sha256'

No comparison yet.

Selected file SHA-256

The checksum and script come from the same site, not an independent signature. A match does not prove safety, authenticity of upstream dependencies, or suitability for your host. Mutable remote dependencies need separate review.

Read validation and limitations

Requirements

Linux host
Docker installed and running
root privileges or sudo
Port 6379 available
/data writable on the host

Best for

Bring up a Redis 7.0.5 instance quickly on a Docker-ready host
Keep Redis data and config under /data/redis7.0.5 on the host
Standardize a reviewed bootstrap path for caches, queues, or session stores

Highlights

Creates /data/redis7.0.5/data and conf automatically
Pulls redis:7.0.5 and runs it as a password-protected container
Generates a strong password automatically if you do not provide one
Writes appendonly and basic persistence settings into the baseline redis.conf

Recommended procedure

Confirm Docker is already installed and the host can expose port 6379.
Run the helper.sh command with sudo or as root.
Let the script prepare /data/redis7.0.5, pull redis:7.0.5, and create the container.
Verify PONG with the effective password before application handoff. If redis.conf already exists, the printed/generated password may differ from its requirepass; protect both the config and console output.

Safety notes

Do not expose Redis directly to the public internet without network controls.
Record the generated password immediately if you did not provide one.
Back up /data/redis7.0.5 before replacing or recreating a production container.

Compatibility and limits

Requires Linux with systemd, Docker, root, a writable data directory, and the selected free host port (6379 by default). redis:7.0.5 is a fixed historical version; this is a compatibility example.
Accepts --data-dir, --container-name, --port and --password, or REDIS_PASSWORD. No dry-run, backup or automatic rollback. Passwords are written into redis.conf and printed; the health check also passes them in process arguments. The script does not escape arbitrary passwords for Redis configuration syntax.
An existing conf/redis.conf is retained. A newly supplied/generated password does not replace its requirepass value. The printed password and CLI exit-status health check are not proof of successful authentication.

Files, services, and data affected

Creates /data/redis7.0.5/data and conf by default. Only a missing redis.conf gets bind 0.0.0.0, protected-mode yes, appendonly yes, snapshot rules and requirepass.
Starts Docker if inactive, pulls redis:7.0.5, force-removes a same-name container, and creates a restartable one. Binds the data directory and read-only config, publishing the selected host port to container 6379 without a host-address restriction. Data and config are reused without backup.

Read-only verification

Substitute custom names/paths if used. Check `docker ps --filter name=redis705`, `docker logs --tail 100 redis705`, and `docker inspect redis705 --format '{{json .Mounts}} {{json .HostConfig.PortBindings}}'`.
Check non-secret configuration with `sudo grep -nE '^(bind|port|protected-mode|appendonly|dir) ' /data/redis7.0.5/conf/redis.conf`.
Use `docker exec -it redis705 redis-cli --askpass PING` and enter the effective password at the prompt. Verify the actual PONG reply, then separately verify application access and retained data. The script only checks command exit status, not reply contents.

If it fails

If credentials or readiness fail, preserve data and redis.conf and check whether an existing file holds a different password. Review ownership, published ports and container logs privately. The completion banner can follow a warning-only readiness failure. Resolve the configuration and back up data before another replacement; a new password option alone does not rotate an existing config.

Redis CLI

Download, inspect, then verify the version before execution. A hash only identifies these exact bytes; it does not prove safety. Piped commands run remote content immediately, and upstream dependencies can change.

Scenario article

Redis prints a new password but authentication still fails

Trace the retained redis.conf before retrying the Redis 7.0.5 installer. Verify actual replies without putting passwords in shared commands or deleting data.

Read article

Docker services: check the interface and retained state

Choose by protocol, data directory and replacement impact: HTTP, SQL, cache, FastCGI or an image-baked application.

Open topic