mirror of
https://github.com/dokku/dokku.git
synced 2025-12-29 00:25:08 +01:00
45c180368f
- Add application name and contents of Procfile as required debug info - Capitalize a few things [ci skip]
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
Description of problem:
|
|
|
|
|
|
Output of the following commands
|
|
|
|
- `uname -a`:
|
|
- `free -m`:
|
|
- `docker version`:
|
|
- `docker -D info`:
|
|
- `sigil -v`:
|
|
- `docker run -ti gliderlabs/herokuish:latest herokuish version`:
|
|
- `dokku version`:
|
|
- `dokku plugin`:
|
|
- `docker inspect CONTAINER_ID` (if applicable):
|
|
(BEWARE: `docker inspect` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
|
|
- `cat /home/dokku/<app>/nginx.conf` (if applicable):
|
|
- Link to the exact repository being deployed (if possible/applicable):
|
|
- If a deploy is failing:
|
|
- Application name
|
|
- The type of application being deployed (node, php, python, ruby, etc.)
|
|
- Whether or not you have a `Dockerfile` in the root of your repository
|
|
- If using buildpacks, which custom buildpacks are in use
|
|
- If it exists, the contents of your `Procfile`.
|
|
- Output of failing dokku commands after running `dokku trace on`
|
|
(BEWARE: `trace on` will print environment variables for some commands, be sure you're not exposing any sensitive information when posting issues. You may replace these values with XXXXXXX):
|
|
|
|
Environment details (AWS, VirtualBox, physical, etc.):
|
|
|
|
How was dokku installed?:
|
|
|
|
How reproducible:
|
|
|
|
|
|
Steps to Reproduce:
|
|
1.
|
|
2.
|
|
3.
|
|
|
|
Actual Results:
|
|
|
|
|
|
Expected Results:
|
|
|
|
|
|
Additional info:
|