mardi 2 janvier 2018

docker moby integration testing fail

I am trying to build from the scratch docker on ARM64 platforms. What I did is as follows: 1. downloading docker binaries to use them as a pre-built docker 2. git clone moby && cd moby 3. make test-integration

It seems like the make commands successfully built docker-dev container. However, make test-integration failed with an error that I have no clue:

=== RUN   TestDaemonRestartKillContainers/live-restore=true/container_with_restart=always/stop-daemon
--- FAIL: TestDaemonRestartKillContainers (0.00s)
    --- PASS: TestDaemonRestartKillContainers/live-restore=true/container_without_restart_policy/kill-daemon (4.09s)
        daemon.go:285: [de494956cf94a] waiting for daemon to start
        daemon.go:317: [de494956cf94a] daemon started
        daemon.go:285: [de494956cf94a] waiting for daemon to start
        daemon.go:317: [de494956cf94a] daemon started
        daemon.go:275: [de494956cf94a] exiting daemon
    --- PASS: TestDaemonRestartKillContainers/live-restore=false/container_without_restart_policy/stop-daemon (6.80s)
        daemon.go:285: [d2e42d53a37e0] waiting for daemon to start
        daemon.go:317: [d2e42d53a37e0] daemon started
        daemon.go:275: [d2e42d53a37e0] exiting daemon
        daemon.go:285: [d2e42d53a37e0] waiting for daemon to start
        daemon.go:317: [d2e42d53a37e0] daemon started
        daemon.go:275: [d2e42d53a37e0] exiting daemon
    --- FAIL: TestDaemonRestartKillContainers/live-restore=false/container_with_restart=always/kill-daemon (7.78s)
        daemon.go:285: [d5471d1c353da] waiting for daemon to start
        daemon.go:285: [d5471d1c353da] waiting for daemon to start
        daemon.go:203: Error starting daemon with arguments: []

The difference I could see is the weird pattern such as d5481d1c353da, or so. I guess that's a container's id. However, how could I know what container is it, and why it failed?

Aucun commentaire:

Enregistrer un commentaire