failing docker tests locally on macOS (case 2)

Bug description

With the latest versions of macOS (Catalina 10.15.4) and Docker CE (2.2.0.5), many of the tests fail to run locally. (This issue was split from #881 after the approach in #882 did not seem to apply to these failures.)

Expected behaviour

Running the test suite locally on a released version of repo2docker should have no errors or failures.

Actual behaviour

A number of tests which require running docker fail. There appear to be a number of different failure messages, many appear to be related to failures using conda or pip to install packages inside the docker container during self.build() invocations. Typical message:

>                           raise docker.errors.BuildError(l["error"], build_log="")
E                           docker.errors.BuildError: The command '/bin/sh -c apt-get -qq update &&     apt-get -qq install --yes        libapparmo
r1        lsb-release        psmisc        sudo        > /dev/null &&     apt-get -qq purge &&     apt-get -qq clean &&     rm -rf /var/lib/apt/lis
ts/*' returned a non-zero code: 100

repo2docker/app.py:729: BuildError
__________________________________________________________________ test session ___________________________________________________________________

    def test():
        app = make_r2d(args)
        app.initialize()
        if app.run_cmd:
            # verify test, run it
            app.start()
            return
        # no run_cmd given, starting notebook server
        app.run = False
>       app.start()  # This just build the image and does not run it.

tests/conftest.py:46: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
repo2docker/app.py:743: in start
    self.build()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Step 1 will be to enumerate and categorized those messages.

How to reproduce

1. On a macOS box, checkout a released version of repo2docker
2. Setup the development environment.
3. invoke pytest tests/
4. observe failures.

Your personal set up

• OS: macOS
• Docker version: CE 2.2.0.5
• repo2docker version: 0.11.4

[betatim]

I vote for “leave as is”. Seems like our time is better spent doing other things than tracking down differences in storage usage, especially if the likely outcome is that we continue to recommend “YMMV, but try making the disk bigger” 😄

[manics]

That bug should’ve been fixed by https://github.com/jupyter/repo2docker/pull/804