v0.18.7

[alexjustesen]

What's Changed

• Use https://crontab.guru instead of https://crontab.cronhub.io/ by @lnlyssg in Use https://crontab.guru instead of https://crontab.cronhub.io/ #1368
• [Bug] Added timezone to latest speedtest API response by @alexjustesen in [Bug] Added timezone to latest speedtest API response #1377
• [Chore] Added deprecated image warning to admin panel by @alexjustesen in [Chore] Added deprecated image warning to admin panel #1380
• Release v0.18.7 by @alexjustesen in Release v0.18.7 #1381

New Contributors

• @lnlyssg made their first contribution in Use https://crontab.guru instead of https://crontab.cronhub.io/ #1368

Full Changelog: v0.18.6...v0.18.7

---

This discussion was created from the release v0.18.7.

[seh2000]

Hi,
When I was installing image v0.18.4 a few weeks back I reported a error happening at the installation.

I followed the recommended approach: I'm not specifically using Python in my application so I'd recommend stopping the container and deleting the image and pulling it again. Also make sure you're using the LSIO one.
Which I did, with the result the issue gone. However, for the next images v0.18.5, v0.18.6 and now with image v0.18.7 I get the same error.
Each time I have stopped the container, deleted the image(s), removed the DB and removed docker then done a fresh install of docker, then reinstalled the image using LSIO (image: lscr.io/linuxserver/speedtest-tracker:0.18.6), which resulted latest image installed and app running.
I just wonder why this started happening with and with subsequent images after image v0.18.4 as before I had no issue and it keeps happening despite going through the same process each time.
If I don't do the above process, but use the image that was working e.g. v0.18.6 no error and the app runs again. If I use a image previous to the one that was working e.g. v0.18.5 same error pops up. If I then goes back to the image that worked e.g. V0.18.6 no error and app works again.

I also tried with this command docker-compose up -d && docker-compose logs -f but didn't get anymore information.
Suggestions? Any logs I should try to get or?
Help much appreciated.
Steen

Below the error:
docker-compose up -d
speedtest-tracker_db_1 is up-to-date
Recreating f62eb274e0bb_speedtest-tracker ...
ERROR: for f62eb274e0bb_speedtest-tracker 'ContainerConfig'
ERROR: for speedtest-tracker 'ContainerConfig'
Traceback (most recent call last):
File "/usr/local/bin/docker-compose", line 8, in sys.exit(main())
File "/usr/local/lib/python3.9/dist-packages/compose/cli/main.py", line 81, in main command_func()
File "/usr/local/lib/python3.9/dist-packages/compose/cli/main.py", line 203, in perform_command handler(command, command_options)
File "/usr/local/lib/python3.9/dist-packages/compose/metrics/decorator.py", line 18, in wrapper result = fn(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/compose/cli/main.py", line 1186, in up to_attach = up(False)
File "/usr/local/lib/python3.9/dist-packages/compose/cli/main.py", line 1166, in up return self.project.up(
File "/usr/local/lib/python3.9/dist-packages/compose/project.py", line 697, in up results, errors = parallel.parallel_execute(
File "/usr/local/lib/python3.9/dist-packages/compose/parallel.py", line 108, in parallel_execute raise error_to_reraise
File "/usr/local/lib/python3.9/dist-packages/compose/parallel.py", line 206, in producer result = func(obj)
File "/usr/local/lib/python3.9/dist-packages/compose/project.py", line 679, in do return service.execute_convergence_plan(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 579, in execute_convergence_plan return self._execute_convergence_recreate(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 499, in _execute_convergence_recreate containers, errors = parallel_execute(
File "/usr/local/lib/python3.9/dist-packages/compose/parallel.py", line 108, in parallel_execute raise error_to_reraise
File "/usr/local/lib/python3.9/dist-packages/compose/parallel.py", line 206, in producer result = func(obj)
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 494, in recreate return self.recreate_container(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 612, in recreate_container new_container = self.create_container(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 330, in create_container container_options = self._get_container_create_options(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 921, in _get_container_create_options container_options, override_options = self._build_container_volume_options(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 960, in _build_container_volume_options binds, affinity = merge_volume_bindings(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 1548, in merge_volume_bindings old_volumes, old_mounts = get_container_data_volumes(
File "/usr/local/lib/python3.9/dist-packages/compose/service.py", line 1579, in get_container_data_volumes container.image_config['ContainerConfig'].get('Volumes') or {}
KeyError: 'ContainerConfig'

[seh2000]

No, I followed the instructions from here https://pimylifeup.com/raspberry-pi-docker/ and from here https://docs.docker.com/engine/install/debian/ and from here https://www.simplilearn.com/tutorials/docker-tutorial/raspberry-pi-docker
I'll reformat the SD card tomorrow, I didn't do before as I am having two other instances running (pihole and UniFi Network Controller), but I'll reinstall those too.

[lnlyssg]

The main reason I asked is because docker-compose has been replaced by docker compose and the fact you are getting python errors looked like it may have been the old deprecated v1 of compose installed via pip that was in use. Could you try using docker compose instead and see if that makes a difference?

[seh2000]

Sure will do
Also you can suggest a good link to How to Install Docker?

[lnlyssg]

I would always go with the official guide (that you already posted) at https://docs.docker.com/engine/install/debian/. If you have followed any other guides in the past that could be the cause of the problem. You can run docker-compose version and docker compose version to see if they are in fact different versions.

[seh2000]

Thanks, I'll start from zero, as it looks like I have both versions installed.
docker-compose version
Docker Compose version v2.12.2

docker compose version
Docker Compose version v2.26.1