Open kit-ty-kate opened 3 years ago
Very odd. According to the logs, this has happened a few times, e.g.
x86-bm-10.ocamllabs.io : ./2021-05-18/115511-ci-ocluster-build-397cc5.log:time="2021-05-18T12:41:08Z" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting \"/etc/resolv.conf\" to rootfs at \"/var/cache/obuilder/result-tmp/99d6e45f1a9c19040352ca54a2b330beb581baeea762c33bfd14b1fc529f1743/rootfs/etc/resolv.conf\" caused: no such file or directory"
x86-bm-6.ocamllabs.io : ./2021-05-18/115540-ci-ocluster-build-e7244a.log:time="2021-05-18T18:13:40Z" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting \"/etc/resolv.conf\" to rootfs at \"/var/cache/obuilder/result-tmp/074efebd0a66bc546ff8975b00cb53b88b7ad6910ee3ae3c033ff3fcde17580b/rootfs/etc/resolv.conf\" caused: no such file or directory"
x86-bm-7.ocamllabs.io : ./2021-05-24/091057-ci-ocluster-build-242081.log:time="2021-05-24T09:15:25Z" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting \"/etc/resolv.conf\" to rootfs at \"/var/cache/obuilder/result-tmp/87ca3d365af464bc84ff9c6988ba26c7344127c0f3a30d100745f00a98399b0f/rootfs/etc/resolv.conf\" caused: no such file or directory"
x86-bm-7.ocamllabs.io : ./2021-05-24/174327-ci-ocluster-build-c2cd26.log:time="2021-05-24T18:30:19Z" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting \"/etc/resolv.conf\" to rootfs at \"/var/cache/obuilder/result-tmp/69b99dd975b9ba10c89e0a785f30dd5caded51ace6cf0eeb1601d2ebca2e1120/rootfs/etc/resolv.conf\" caused: no such file or directory"
x86-bm-4.ocamllabs.io : ./2021-05-26/144123-ci-ocluster-build-9ac277.log:time="2021-05-26T20:03:55+02:00" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting \"/etc/resolv.conf\" to rootfs at \"/var/cache/obuilder/result-tmp/0203f4883069487f59561fb1c11e7f3be73e79276b91868f5f6cc45d301383d9/rootfs/etc/resolv.conf\" caused: no such file or directory"
It happened again. It seems to be unique to the x86-bm-*
machines so far: https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/1bba005b68d8441bdd86f1bffc220b8e6f623732/variant/opam-2.1,distributions,archlinux,h1_parser.0.0.2,tests
Another occurence in https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/f9b6838562de5a899902de01ea3351cdb4bf185f/variant/opam-2.0,distributions,ubuntu-18.04,irmin-chunk.2.7.0,tests
time="2021-06-23T20:07:12+02:00" level=error msg="container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: rootfs_linux.go:59: mounting \"/etc/resolv.conf\" to rootfs at \"/var/cache/obuilder/result-tmp/a2708450d72d53b2c74e292c16fc938209e0b10d309ae5a8f833ce16963f3a70/rootfs/etc/resolv.conf\" caused: no such file or directory"
Full log: https://opam.ci.ocaml.org/github/ocaml/opam-repository/commit/ec85e6548c1148414fca1d6e4f407d805e995776/variant/opam-2.0,distributions,oraclelinux-8,bimage-lwt.0.4.0,tests