• Members 8 posts
    Aug. 14, 2020, 3:43 a.m.

    I'm using Google Translate, sorry for errors

    I think I found a bug, or it could be that some mistake of mine caused it

    Sorry if I'm reporting in the wrong place

    When I run ./appctl bash I get: ERROR: No container found for misago_1

    I changed the appctl from:

    run_bash () {
    docker-compose exec misago bash
    }

    For:

    run_bash () {
    docker-compose run misago bash
    }

    and apparently it worked

  • Aug. 14, 2020, 12:28 p.m.

    Which version of docker and docker-compose are you using? This container should exist whex exec is called.

  • Members 8 posts
    Aug. 14, 2020, 10:59 p.m.

    installed by default ubuntu 18.04 LTS repositories

    docker version:

    Client:
    Version: 19.03.6
    API version: 1.40
    Go version: go1.12.17
    Git commit: 369ce74a3c
    Built: Fri Feb 28 23:45:43 2020
    OS/Arch: linux/amd64
    Experimental: false

    Server:
    Engine:
    Version: 19.03.6
    API version: 1.40 (minimum version 1.12)
    Go version: go1.12.17
    Git commit: 369ce74a3c
    Built: Wed Feb 19 01:06:16 2020
    OS/Arch: linux/amd64
    Experimental: false
    containerd:
    Version: 1.3.3-0ubuntu1~18.04.2
    GitCommit:
    runc:
    Version: spec: 1.0.1-dev
    GitCommit:
    docker-init:
    Version: 0.18.0
    GitCommit:

    docker-compose version:

    docker-compose version 1.17.1, build unknown
    docker-py version: 2.5.1
    CPython version: 2.7.17
    OpenSSL version: OpenSSL 1.1.1 11 Sep 2018

  • Aug. 15, 2020, 11:50 a.m.
    check_box

    Marked as best answer by Aug. 18, 2020, 12:02 a.m..

    Did you run „appctl setup” before trying to access bash? „exec” is used instead of „run” because „run” starts new container and „exec” connects to already running obe.

    If „exec” failed you should debug why there were no containers running.