Many thanks for the useful pointer…
To set up a new container with V1 compatibility (I’ve tried to break it down into baby steps…)
a) Create a setup with admin user and org name with a primary bucket (If setting ‘–retention 0’ gives you and error set it to something like ‘–retention 52w’
influx setup --username administrator --password administrator --token MyTokenMyToken== --org MyOrgName --bucket sandbox --retention 0
b) I don’t seem to have any way of specifying the bucket ID… so I need to find out what it is. From this command, I find from here:
# influx bucket list
ID Name Retention Organization ID
af51c518b079e1c7 _monitoring 168h0m0s 1c49c5b0f4e4619f
c49c80722eb63f89 _tasks 72h0m0s 1c49c5b0f4e4619f
9b9841b1ecb10e16 sandbox 8736h0m0s 1c49c5b0f4e4619f <<--------
c) Next provide authorization for v1.x -> I tried this: (If specifying --password gives ‘Error: unknown flag’ error, remove it and set manually)
influx v1 auth create --read-bucket 9b9841b1ecb10e16 --write-bucket 9b9841b1ecb10e16 --username administrator --password administrator
d) Map the v1 database to the v2 bucket
influx v1 dbrp create --bucket-id 9b9841b1ecb10e16 --db sandboxDB --rp 0
e) To summarise so far…
# influx v1 auth list
ID Description Name / Token User Name User ID Permissions
06b5ffe180d6a000 administrator administrator 06b5fa6c0816a000 [read:orgs/1c49c5b0f4e4619f/buckets/9b9841b1ecb10e16 write:orgs/1c49c5b0f4e4619f/buckets/9b9841b1ecb10e16]
# influx v1 dbrp list
ID Database Bucket ID Retention Policy Default Organization ID
06b601d7a416a000 sandboxDB 9b9841b1ecb10e16 0 true 1c49c5b0f4e4619f
Back to the Vibrant C# client - When doing a simple database ‘list’ command I see the newly linked ‘sandboxDB’ - success!
However - any operation on ‘sandboxDB’ returns a server error.
I’m surprised none of the settings above have appeared in the /root/.influxdbv2/configs file. Where does this stuff go - if not in configs?
Any nudge in the right direction welcome… I’m sure its easy when you know how. Oh well, back to work!
Additional comments:
I see there are some recent commits on this… So I follow the download nightly instructions for 2.x:
docker pull quay.io/influxdb/influxdb:nightly
Which gets me this:
quay.io/influxdb/influxdb IN USE nightly b8c6c4f59e84 19 minutes ago 275.55 MB
I add the image to the container using this:
docker run --name influxdb -p 8086:8086 quay.io/influxdb/influxdb:nightly
But suprisingly, checking the version gives me this:
# influx -version
InfluxDB shell version: 1.7.0~n201901110800
Enter an InfluxQL query
I guess using the nightly build system is just not for me!
Back to the 2.0.2 release instead…
