v0.11.18 #695
Replies: 11 comments 17 replies
-
|
Just a heads up, I am aware of a dependency preventing this version from building and will look at it later this week. |
Beta Was this translation helpful? Give feedback.
-
|
@alexjustesen |
Beta Was this translation helpful? Give feedback.
-
|
strange, for me 0.11.17 is still the latest I can't pull 0.11.18... If I change the image tag to 0.11.18 I get the manifest unknown error (probably the container image is missing... |
Beta Was this translation helpful? Give feedback.
-
|
Correct, the image never built successfully so you can't pull it. |
Beta Was this translation helpful? Give feedback.
-
|
@alexjustesen |
Beta Was this translation helpful? Give feedback.
-
It's only been removed as the default install option when setting up a new instance so if you're already using it it'll continue to work. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a writeup somewhere for a dummy like myself on how to set up the docker compose file correctly? I'm trying to use MariaDB. Copy/pasting from the docs is erroring out for me. I set up an .envcompose.yamlversion: '3.3'
services:
speedtest-tracker:
container_name: ${CNAME}
ports:
- '8080:80'
- '8443:443'
networks:
- network1
environment:
- PUID=${PUID}
- PGID=${PGID}
- DB_CONNECTION=mysql
- DB_HOST=db
- DB_PORT=3306
- DB_DATABASE=${MARIADB_DATABASE}
- DB_USERNAME=${MARIADB_USER}
- DB_PASSWORD=${MARIADB_PASSWORD}
- TZ=${TZ}
volumes:
- '/etc/localtime:/etc/localtime:ro'
- '${DOCKER_DIR}/${CNAME}:/config'
image: 'ghcr.io/alexjustesen/speedtest-tracker:latest'
restart: unless-stopped
depends_on:
- db
db:
image: mariadb:10
restart: always
networks:
- network1
environment:
- MARIADB_DATABASE=${MARIADB_DATABASE}
- MARIADB_USER=${MARIADB_USER}
- MARIADB_PASSWORD=${MARIADB_PASSWORD}
- MARIADB_RANDOM_ROOT_PASSWORD=true
volumes:
- speedtest-db:/var/lib/mysql
volumes:
speedtest-db:
networks:
network1:
name: prod
external: truerunning
|
Beta Was this translation helpful? Give feedback.
-
|
@luckman212 try removing the environment variables with the |
Beta Was this translation helpful? Give feedback.
-
|
@alexjustesen But the |
Beta Was this translation helpful? Give feedback.
-
|
@alexjustesen Following up, I eventually got this working. Running on 0.11.20 + MariaDB + Synology now. Putting my docker compose config up as a gist in case it helps anyone. The TL;DR key was just needing to be more patient and wait long enough for MariaDB to start up. |
Beta Was this translation helpful? Give feedback.
-
|
Adding for any other poor unfortunate soul who made my mistake. I got this exact same error, but my mariadb instance is a standalone container used for a couple different configurations and therefore didn't need time to spin up. My error was that I named my username and database the same thing. I changed the username to "speedy" and the database to something else and it worked the first time. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/alexjustesen/speedtest-tracker/releases/tag/v0.11.19 was tagged which resolved the build issue in |
Beta Was this translation helpful? Give feedback.
-
No, you are defining the env variables both in docker-compose AND the .env file. Either use one or the other. Another thing: since you use Synology, install mariadb as a NAS package, create the speedtest db, create a user, assign permissions to the user for the db, then in docker-compose you can remove the db service that starts mariadb completely. So you only configure the speedtest section with the user/pw to access the synology mariadb instance. Last thing: I suspect you probably created the db the first time with a different user or different pw. When you change it, the old db won't get changed because the volume is persistent. So you might want to stop the container, remove the volume, and restart from scratch. |
Beta Was this translation helpful? Give feedback.
-
|
I have made sure to delete the volumes and all persistent data and start 100% fresh. I also manually edited the compose file to pull v0.11.19 since As for the .env file, yes I know there is an .env for the container itself that holds stuff like the SMTP config, but I am talking about the .env for docker-compose, which is separate and I believe the correct way to pass shell vars into a compose file: https://docs.docker.com/compose/environment-variables/set-environment-variables/ I know this is not best practice, and I should use secrets instead, but I haven't had time to learn that yet. As for installing MariaDB package from Synology, I had thought of that, but I wanted the containers to be managed together, to avoid problems when the db package gets updated etc, since it would not automatically pause the container if not managed by docker-compose. Also, I don't know how to create the database, tables and permissions needed—Is this handled automatically during the main container init?
edit: finally [got it working] 🎉 (https://gist.github.com/luckman212/40ff0a827c12007c8c79ff275d390767) |
Beta Was this translation helpful? Give feedback.
-
|
Have opened this bug here - #701 for 0.11.19 which just updated but is failing! |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/alexjustesen/speedtest-tracker/releases/tag/v0.11.20 rolling out to fix it |
Beta Was this translation helpful? Give feedback.
-
|
woke up this morning and my 5 instances of this have stopped working. I came here and saw this, and also in the docs the docker install is different. Should I just destroy all these and rebuild with the new compose? |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/alexjustesen/speedtest-tracker/releases/tag/v0.11.20 rolling out to fix it |
Beta Was this translation helpful? Give feedback.
-
|
@alexjustesen @alexdelprete |
Beta Was this translation helpful? Give feedback.
-
|
What the other Alex said, no auto import. |
Beta Was this translation helpful? Give feedback.
-
no automatic procedure yet. |
Beta Was this translation helpful? Give feedback.
-
|
@alexdelprete |
Beta Was this translation helpful? Give feedback.
-
|
updated overnight and all mine started working again without me having to do anything at all. thank you!! |
Beta Was this translation helpful? Give feedback.
-
|
@alexjustesen @alexdelprete |
Beta Was this translation helpful? Give feedback.
-
You can't in this release. In next release there will be a specific command: |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Using version 0.18.3 via Docker on Debian 12, I'm experiencing the following error when running What to do ? Thanks |
Beta Was this translation helpful? Give feedback.
-
What's Changed
Full Changelog: v0.11.17...v0.11.18
This discussion was created from the release v0.11.18.
Beta Was this translation helpful? Give feedback.
All reactions