Ring not yet ready, read/writes will be lost! #965
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind/experimental
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#965
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
HI there, thanks for this S3 software!
I'm trying this software: I can create a layout, apply it, create a bucket, create a key, assign it to the bucket, but I still get the first lines of errors below, and each restart of my docker container make me loss all the config / buckets / keys created.
I don't understand how to correct that
I have Garage as a Docker container, with Traefik as reverse proxy: below is my docker compose
2025-02-19T08:03:08.988976Z WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost!
2025-02-19T08:03:08.988981Z WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost!
2025-02-19T08:03:08.988987Z WARN garage_rpc::layout::version: Ring not yet ready, read/writes will be lost!
2025-02-19T08:03:08.988995Z INFO garage_table::sync: k2v_index_counter_v2: Adding full sync for ack layout version 0
2025-02-19T08:03:08.989240Z INFO garage_table::sync: bucket_v2: Completed full sync for ack layout version 0
2025-02-19T08:03:08.989345Z INFO garage_table::sync: bucket_alias: Completed full sync for ack layout version 0
2025-02-19T08:03:08.989432Z INFO garage_table::sync: key: Completed full sync for ack layout version 0
2025-02-19T08:03:09.083971Z INFO garage_table::sync: object: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084170Z INFO garage_table::sync: bucket_object_counter: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084284Z INFO garage_table::sync: multipart_upload: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084401Z INFO garage_table::sync: bucket_mpu_counter: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084509Z INFO garage_table::sync: version: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084654Z INFO garage_table::sync: block_ref: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084762Z INFO garage_table::sync: k2v_item: Completed full sync for ack layout version 0
2025-02-19T08:03:09.084856Z INFO garage_table::sync: k2v_index_counter_v2: Completed full sync for ack layout version 0
And the garage.toml is:
Your
garage.toml
configuration file is wrong, you have to specifydata_dir
andmetadata_dir
paths within the Docker container (/var/lib/garage/...
) and not on the host system.Many thanks Alex, this enabled me to correct a get my Garage S3 up and running! Currently understanding / testing its capacities.
I still have for some reason a strange behavior where not every time I can access my external S3 endpoint from the internet, but I suspect it has more to do with my Traefik proxy (strange though because I have 50 other containers running where I don't have that sort of issue). If I change a setting in my Traefik section of the Garage docker compose, and restart the container, it usually corrects the external connectivity.