Docker setup no longer works

[dch0ph]

Screenshots with links illustrating the problem

Testing the instructions in Docker.md, the docker compose up import fails at RUN apt-key (as above)

The warning is presumably from the message that apt-key is deprecated, and it then hangs with no response from the key server.

The current Dockerfile is based on a now quite old version of Ubuntu (18.04), and there are alternative, and more up-to-date, instructions on Switch2OSM. Although these are more oriented to setting up OSM Carto as part of a full tile server, and don't refer to setting up kosmtik.

Perhaps somebody who uses this route / kosmtik could update/fix the instructions? [Personally I find it easier to test rendering / output maps from printing using the python mapnik bindings and nik4.py]

[pnorman]

I don't see an error there. The warning is fine. I know keyserver.ubuntu.com sometimes times out. Moving to a more recent OS would avoid the need for PPAs and make this line moot.

Should we remove the docker setup? I don't think we have enough people involved that we can keep it working.

[dch0ph]

All the times I have tried it, it hangs waiting for the keyserver, although this could be a problem at my end, rather than reflecting the deprecated `apt-key' (which was my assumption). So, yes, not strictly an error, but still a fail.

I'm not convinced that the docker setup is worth maintaining. If people are installing a tile server, then there are more up-to-date instructions elsewhere. If they are wanting to develop the style, then they probably want a more general development environment (which might involve a docker container).

[imagico]

I think we need someone to commit to (at least from time to time) look after the docker setup or otherwise should remove it.

It would be nice to have this available for sure because i suspect quite a few new contributors have in the past used docker as a starting point for getting into OSM-Carto development and it could continue to serve as such. But things are as they are, this is a volunteer project, we can only do things for which people volunteer their capacity.

So again: This is a field were help would be much appreciated. Anyone with some experience with Docker who is interested in maintaining our docker setup for style developers is highly welcome. Starting point would be to evaluate the current state and see where maintenance is required and to submit necessary changes as PRs. Beyond that reviewing PRs that affect the docker setup (like #4978) would also be important.