# History ## 0.37.0 Install/update via the bootstrap script: ```shell wget -NP . https://dokku.com/install/v0.37.0/bootstrap.sh sudo DOKKU_TAG=v0.37.0 bash bootstrap.sh ``` See the [0.37.0 migration guide](/docs/appendices/0.37.0-migration-guide.md) for more information on migrating to 0.37.0. ### Backwards Compatibility Breaks - #8140: @josegonzalez Rename the scheduler-k3s:cluster-* commands to use a : instead of - for a delimiter - #7982: @josegonzalez Remove references to pack being experimental ### Bug Fixes - #8136: @josegonzalez Do not reset manually set port mappings when upgrading dokku - #8114: @josegonzalez Ensure we can execute run commands when exec is executed as part of an entrypoint - #8109: @josegonzalez Allow skipping the install trigger when installing a plugin - #8104: @josegonzalez Drop deprecated aufs check - #8100: @othercorey Add process-type label for run with procfile cmd ### New Features - #8139: @josegonzalez Add aliases for select builder and scheduler plugins - #8138: @josegonzalez Turn on buildpack trace mode when dokku trace is on - #8137: @josegonzalez Add the ability to create k3s node profiles - #8135: @josegonzalez Add support for git remotes with port specified inline - #8112: @josegonzalez Implement cron and one-off run task TTLs - #8106: @josegonzalez Support inline comments for app.json - #8105: @josegonzalez Allow specifying kubelet-args when adding a new node to the cluster - #8085: @josegonzalez Implement config:import command - #8004: @Tashows Add buildpacks:detect subcommand - #7991: @josegonzalez Add ability to pause/restart cron jobs - #7989: @josegonzalez Add support to prevent overlapping execution of cron tasks - #7986: @josegonzalez Add support for specifying CNB buildpacks via buildpacks command - #7956: @josegonzalez Add a Railpack builder to Dokku - #7608: @dragonhunt02 Add commands to proxy implementations for managing labels ### Refactors - #8101: @josegonzalez Filter build docker-options correctly for each builder ### Documentation - #8103: @josegonzalez Correct the release version for railpacks support ### Dependencies - #8130: @dependabot[bot] chore(deps): bump golang.org/x/crypto from 0.43.0 to 0.45.0 in /plugins/common - #8110: @dependabot[bot] chore(deps): bump google.golang.org/grpc from 1.76.0 to 1.77.0 in /tests/apps/gogrpc - #8108: @dependabot[bot] chore(deps): bump js-yaml from 3.14.1 to 3.14.2 in /tests/apps/multi - #8107: @dependabot[bot] chore(deps): bump click from 8.3.0 to 8.3.1 in /docs/_build - #8098: @dependabot[bot] chore(deps): bump traefik from 3.5.4 to 3.6.1 in /plugins/traefik-vhosts - #8097: @dependabot[bot] chore(deps): bump timberio/vector from 0.51.0-debian to 0.51.1-debian in /plugins/logs - #8094: @dependabot[bot] chore(deps): bump pymdown-extensions from 10.16.1 to 10.17.1 in /docs/_build - #8092: @dependabot[bot] chore(deps): bump mkdocs-material from 9.6.23 to 9.7.0 in /docs/_build - #8090: @dependabot[bot] chore(deps): bump sigs.k8s.io/kustomize/api from 0.20.1 to 0.21.0 in /plugins/scheduler-k3s
118 lines
4.0 KiB
Markdown
118 lines
4.0 KiB
Markdown
# Docker Installation Notes
|
|
|
|
Pull the dokku/dokku image:
|
|
|
|
```shell
|
|
docker pull dokku/dokku:0.37.0
|
|
```
|
|
|
|
Next, run the image.
|
|
|
|
```shell
|
|
docker container run -d \
|
|
--env DOKKU_HOSTNAME=dokku.me \
|
|
--env DOKKU_HOST_ROOT=/var/lib/dokku/home/dokku \
|
|
--env DOKKU_LIB_HOST_ROOT=/var/lib/dokku/var/lib/dokku \
|
|
--name dokku \
|
|
--publish 3022:22 \
|
|
--publish 8080:80 \
|
|
--publish 8443:443 \
|
|
--volume /var/lib/dokku:/mnt/dokku \
|
|
--volume /var/run/docker.sock:/var/run/docker.sock \
|
|
dokku/dokku:0.37.0
|
|
```
|
|
|
|
Alternatively, you can use `docker-compose.yml`:
|
|
|
|
```yaml
|
|
services:
|
|
dokku:
|
|
image: dokku/dokku:0.37.0
|
|
container_name: dokku
|
|
network_mode: bridge
|
|
ports:
|
|
- "3022:22"
|
|
- "8080:80"
|
|
- "8443:443"
|
|
volumes:
|
|
- "/var/lib/dokku:/mnt/dokku"
|
|
- "/var/run/docker.sock:/var/run/docker.sock"
|
|
environment:
|
|
DOKKU_HOSTNAME: dokku.me
|
|
DOKKU_HOST_ROOT: /var/lib/dokku/home/dokku
|
|
DOKKU_LIB_HOST_ROOT: /var/lib/dokku/var/lib/dokku
|
|
restart: unless-stopped
|
|
```
|
|
|
|
The above command will start a new docker container that is ready when a message similar to `Runit started as PID 12345` appears.
|
|
|
|
Dokku is run in the following configuration:
|
|
|
|
- The global hostname is set to `dokku.me` on boot.
|
|
- The container name is dokku.
|
|
- Container SSH port 22 is exposed on the host as 3022.
|
|
- Container HTTP port 80 is exposed on the host as 8080.
|
|
- Container HTTPS port 443 is exposed on the host as 8443.
|
|
- Data within the container is stored on the host within the `/var/lib/dokku` directory.
|
|
- Image build cache is set to the data dir + `/home/dokku`.
|
|
- The docker socket is mounted into container.
|
|
|
|
Application repositories, plugin config, as well as plugin data are persisted to disk within the specified host directory for `/var/lib/dokku`.
|
|
|
|
Other docker container options can also be used when running Dokku, though the specific outcome will depend upon the specified options. For example, the Dokku container's nginx port can be bound to a specific host ip by specifying `--publish $HOST_IP:8080:80`, where `$HOST_IP` is the IP desired. Please see the [docker container run documentation](https://docs.docker.com/engine/reference/commandline/run/) for further explanation for various docker arguments.
|
|
|
|
## Plugin Installation
|
|
|
|
### On Dokku start
|
|
|
|
To install custom plugins, create a `plugin-list` file in the host's `/var/lib/dokku` directory. The plugins listed herein will be automatically installed by Dokku on container boot. This file should be the following format:
|
|
|
|
```yaml
|
|
plugin_name: repository_url
|
|
```
|
|
|
|
An example for installing the postgres and redis plugins follows:
|
|
|
|
```yaml
|
|
postgres: https://github.com/dokku/dokku-postgres.git
|
|
redis: https://github.com/dokku/dokku-redis.git
|
|
```
|
|
|
|
### Prior to Dokku start
|
|
|
|
The alternative is to build a custom docker image via a custom Dockerfile. This Dockerfile can run any `plugin:install` command. Note that the version installed at that time will be the one that persists. Below is an example Dockerfile showing this method.
|
|
|
|
```Dockerfile
|
|
FROM dokku/dokku:0.37.0
|
|
RUN dokku plugin:install https://github.com/dokku/dokku-postgres.git --skip-install-trigger
|
|
RUN dokku plugin:install https://github.com/dokku/dokku-redis.git --skip-install-trigger
|
|
```
|
|
|
|
## SSH Key Management
|
|
|
|
To initialize ssh-keys within the container, use `docker exec` to enter the container:
|
|
|
|
```shell
|
|
docker exec -it dokku bash
|
|
```
|
|
|
|
Next, run the appropriate ssh-keys commands:
|
|
|
|
```shell
|
|
echo "$CONTENTS_OF_YOUR_PUBLIC_SSH_KEY_HERE" | dokku ssh-keys:add KEY_NAME
|
|
```
|
|
|
|
Please see the [user management documentation](/docs/deployment/user-management.md) for more information.
|
|
|
|
## Pushing Applications
|
|
|
|
When exposing the Dokku container's SSH port (22) on 3022, something similar to the following will need to be setup within the user's `~/.ssh/config`:
|
|
|
|
```
|
|
Host dokku.docker
|
|
HostName 127.0.0.1
|
|
Port 3022
|
|
```
|
|
|
|
In the above example, the hostname `127.0.0.1` is being aliased to `dokku.docker`, while the port is being overridden to `3022`. All SSH commands - including git pushes - for the hostname `dokku.docker` will be transparently sent to `127.0.0.1:3022`.
|