-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iox-gc container fails to start - missing influxdb_iox binary #7
Comments
Hello, Stranger! Please star this repository to motivate developers! ⭐ |
Hello @mugen6 sadly the folks at influx keep making changes and chopping features off iox (compared to its initial form, as you can see from the binary loosing significant size from iox to influxdb3) and the original instructions and settings are no longer producing the expected results. I'm not sure what the future holds for InfluxDB3 but at the moment its no longer seems to be the IOx we were invested into and it became some sort of "opencore" minimal version lacking major features. You can see we still provide the older full featured build |
Hi @lmangani, thanks for such a quick response. That is a shame to hear, because after evaluating several time series DBs, Influx 3.0 looked to tick all the right boxes. What other DBs are you looking at, if you were to abandon Influx? So I can run the influx_iox binary but if I wanted to get this working in Docker, do I just rebuild the docker image with the old binary? |
I share the sentiment and still have hope for it to be fully opensourced again. This is the "old" full featured iox container: https://github.com/metrico/iox-community/pkgs/container/iox-musl |
Thanks for putting this together - InfluxDB 3.0 is looking very promising.
I started with a fresh VM with docker and did the following:
git clone https://github.com/metrico/iox-community.git
docker pull ghcr.io/metrico/influxdb-edge-musl:latest
docker-compose up -d
Got the following errors:
The containers that did come up look like this:
I also get this:
Do I have to change something in the docker-compose.yml?
The text was updated successfully, but these errors were encountered: