这是indexloc提供的服务,不要输入任何密码
Skip to content

Completly remove dokku #2020

@arkryonia

Description

@arkryonia

Description of problem:
I need to remove completly dokku from my server in order to reinstall it. I did with apt-get remove dokku. But I haven't the result I need.

Output of the following commands

  • uname -a:
    Linux rosen 3.16.0-4-amd64 Prerequisite changes to allow Java buildpack support #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux
  • free -m:
    total used free shared buffers cached
    Mem: 1000 907 93 49 155 385
    -/+ buffers/cache: 366 634
    Swap: 0 0 0
  • docker version:
    Client:
    Version: 1.10.3
    API version: 1.22
    Go version: go1.5.3
    Git commit: 20f81dd
    Built: Thu Mar 10 15:38:58 2016
    OS/Arch: linux/amd64

Server:
Version: 1.10.3
API version: 1.22
Go version: go1.5.3
Git commit: 20f81dd
Built: Thu Mar 10 15:38:58 2016
OS/Arch: linux/amd64

  • docker -D info:
    Containers: 1
    Running: 1
    Paused: 0
    Stopped: 0
    Images: 6
    Server Version: 1.10.3
    Storage Driver: aufs
    Root Dir: /var/lib/docker/aufs
    Backing Filesystem: extfs
    Dirs: 38
    Dirperm1 Supported: true
    Execution Driver: native-0.2
    Logging Driver: json-file
    Plugins:
    Volume: local
    Network: null host bridge
    Kernel Version: 3.16.0-4-amd64
    Operating System: Debian GNU/Linux 8 (jessie)
    OSType: linux
    Architecture: x86_64
    CPUs: 1
    Total Memory: 1000 MiB
    Name: rosen
    ID: ZLCP:IGXQ:FSDL:YI6S:KNYZ:TOUU:HIUT:X4LQ:KBH2:S2Z6:AKWP:QRAK
    WARNING: No memory limit support
    WARNING: No swap limit support
    WARNING: No oom kill disable support
    WARNING: No cpu cfs quota support
    WARNING: No cpu cfs period support
  • sigil -v:
    zsh: command not found: sigil
  • docker run -ti gliderlabs/herokuish:latest herokuish version:
    herokuish: 0.3.8
    buildpacks:
    heroku-buildpack-clojure v73
    heroku-buildpack-go v22
    heroku-buildpack-gradle v17
    heroku-buildpack-grails v19
    heroku-buildpack-java v42
    heroku-buildpack-multi v1.0.0
    heroku-buildpack-nodejs v87
    heroku-buildpack-php v90
    heroku-buildpack-play v24
    heroku-buildpack-python v74
    heroku-buildpack-ruby v141
    heroku-buildpack-scala v64
    buildpack-nginx v5
  • dokku version: 0.4.14
  • dokku plugin:
    plugn: dev
    00_dokku-standard 0.4.0 enabled dokku core standard plugin
    20_events 0.4.0 enabled dokku core events logging plugin
    apps 0.4.0 enabled dokku core apps plugin
    backup 0.4.0 enabled dokku core backup plugin
    build-env 0.4.0 enabled dokku core build-env plugin
    certs 0.4.0 enabled dokku core certificate management plugin
    checks 0.4.0 enabled dokku core checks plugin
    common 0.4.0 enabled dokku core common plugin
    config 0.4.0 enabled dokku core config plugin
    docker-options 0.4.0 enabled dokku core docker-options plugin
    domains 0.4.0 enabled dokku core domains plugin
    enter 0.4.0 enabled dokku core enter plugin
    git 0.4.0 enabled dokku core git plugin
    logs 0.4.0 enabled dokku core logs plugin
    named-containers 0.4.0.1 enabled dokku core named containers plugin
    nginx-vhosts 0.4.0 enabled dokku core nginx-vhosts plugin
    plugin 0.4.0 enabled dokku core plugin plugin
    postgres 1.0.0 enabled dokku postgres service plugin
    ps 0.4.0 enabled dokku core ps plugin
    shell 0.4.0 enabled dokku core shell plugin
    tags 0.4.0 enabled dokku core tags plugin
    tar 0.4.0 enabled dokku core tar 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:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions