Posts by mrcyrus

    A few months back several of my docker containers died (transmission, pi-hole). I recreated them using same settings, and even did a complete reinstall but something is wrong.


    In transmission I am unable to connect to trackers. Using portainer i can do a ping from inside the container, and it resolves adresses and all - but still its unable to connect.
    I then installed RUtorrent image - still the same error
    I've verified the trackers are available and I can download just fine using a windows based client.


    what could be wrong?


    ps. I'm using Odroid HC2, armbian

    Client: Docker Engine - Community
    Version: 19.03.1
    API version: 1.40
    Go version: go1.12.5
    Git commit: 74b1e89
    Built: Thu Jul 25 21:35:21 2019
    OS/Arch: linux/arm
    Experimental: false


    Server: Docker Engine - Community
    Engine:
    Version: 19.03.1
    API version: 1.40 (minimum version 1.12)
    Go version: go1.12.5
    Git commit: 74b1e89
    Built: Thu Jul 25 21:29:21 2019
    OS/Arch: linux/arm
    Experimental: false
    containerd:
    Version: 1.2.6
    GitCommit: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
    runc:
    Version: 1.0.0-rc8
    GitCommit: 425e105d5a03fabd737a126ad93d62a9eeede87f
    docker-init:
    Version: 0.18.0
    GitCommit: fec3683


    Client:
    Debug Mode: false


    Server:
    Containers: 4
    Running: 0
    Paused: 0
    Stopped: 4
    Images: 5
    Server Version: 19.03.1
    Storage Driver: overlay2
    Backing Filesystem: extfs
    Supports d_type: true
    Native Overlay Diff: true
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Plugins:
    Volume: local
    Network: bridge host ipvlan macvlan null overlay
    Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: 894b81a4b802e4eb2a91d1ce216b8817763c29fb
    runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f
    init version: fec3683
    Security Options:
    seccomp
    Profile: default
    Kernel Version: 4.14.133-odroidxu4
    Operating System: Debian GNU/Linux 9 (stretch)
    OSType: linux
    Architecture: armv7l
    CPUs: 8
    Total Memory: 1.95GiB
    Name: server
    ID: AGIH:YYDC:TGJG:DHRB:D4H7:BLUB:JRQQ:J6SS:WB7Z:I5YX:H7PO:ODDY
    Docker Root Dir: /srv/dev-disk-by-label-HDD1/docker
    Debug Mode: false
    Registry: https://index.docker.io/v1/
    Labels:
    Experimental: false
    Insecure Registries:
    127.0.0.0/8
    Live Restore Enabled: false

    After Docker update all containers dead - docker itself seem to be working. But all containers give the following error:


    OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/s6-init\": permission denied": unknown


    what could be the cause?

    You must be installing on an arm system?

    Yes, was just following the Cockpit install video from Technodadlife.
    I skipped this step (virtualization), and Cockpit is now installed
    Thanks for your help!

    Ok thanks for that. Errors are gone. But installation fails

    Code
    root@server:/etc/apt# apt-get install virtinst qemu-kvm qemu-utils
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Package qemu-kvm is not available, but is referred to by another package.
    This may mean that the package is missing, has been obsoleted, or
    is only available from another source
    E: Package 'qemu-kvm' has no installation candidate

    had to delete some of it because of posting limit - hope this makes sense

    Hoping for some advice - again :)
    Got docker up and running on Odroid HC2 running OMV 4x. Now i need to get Emby up and running. Found this docker img: embyserver_arm32v7
    but just get errors when running it: