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
Update from 0.13.7 to 0.14.0 crashes container #1482
Comments
Looking at the log, I see that the problem is that there's an invalid database URL being specified. specifically: Are you compiling with |
Hi, I'm just using the docker image you provide. This is my compose file and the env file: --------------------- Start services: ports: networks: ------------------------- Start |
I've tried it again, after it's officially released. The error is the same. What I've not registered before: The image for 0.14.0 is quite larger than for 0.13.7, 2.2 GB to 1.4 GB. Is that normal? |
I yesterday did also the update and I have the same problem, after updating the Container won't start anymore. I'm currently running the syncstorage on a Kubernetes cluster with this deployment: apiVersion: apps/v1
kind: Deployment
metadata:
name: syncstorage
namespace: mozilla
labels:
app: syncstorage
spec:
replicas: 1
selector:
matchLabels:
app: syncstorage
template:
metadata:
labels:
app: syncstorage
spec:
containers:
- name: syncstorage
image: mozilla/syncstorage-rs:0.13.7
ports:
- containerPort: 8000
env:
- name: SYNC_HOST
value: 0.0.0.0
- name: SYNC_MASTER_SECRET
valueFrom:
secretKeyRef:
name: syncstorage
key: masterSecret
- name: SYNC_SYNCSTORAGE__DATABASE_URL
valueFrom:
secretKeyRef:
name: syncstorage
key: syncstorageDatabaseUrl
- name: SYNC_RUN_MIGRATIONS
value: "true"
- name: SYNC_TOKENSERVER__ENABLED
value: "true"
- name: SYNC_TOKENSERVER__RUN_MIGRATIONS
value: "true"
- name: SYNC_TOKENSERVER__NODE_TYPE
value: "mysql"
- name: SYNC_TOKENSERVER__DATABASE_URL
valueFrom:
secretKeyRef:
name: syncstorage
key: tokenserverDatabaseUrl
- name: SYNC_TOKENSERVER__FXA_EMAIL_DOMAIN
value: "api.accounts.firefox.com"
- name: SYNC_TOKENSERVER__FXA_OAUTH_SERVER_URL
value: "https://oauth.accounts.firefox.com/v1"
- name: SYNC_TOKENSERVER__FXA_METRICS_HASH_SECRET
valueFrom:
secretKeyRef:
name: syncstorage
key: fxaMetricsHashSecret
- name: SYNC_TOKENSERVER__ADDITIONAL_BLOCKING_THREADS_FOR_FXA_REQUESTS
value: "2"
tolerations:
- key: "architecture"
operator: "Equal"
value: "x86"
effect: "NoExecute"
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/arch
operator: In
values:
- amd64 |
last night i finally got tired of the issues with this project and decided to move to vaultwarden instead, couldn't be happier so far |
And what has Vaultwarden to do with Firefox Sync? You're talking about two different products, which are doing different things... |
Not really, I used it to sync passwords which I don't want to be stored on Mozilla servers, for the other stuff like bookmarks and settings I really don't care if they are stored on Mozilla servers so for me that's all I need |
But that's not the main goal of Firefox Sync. Otherwise Vaultwarden / Bitwarden is "only" a password safe. And this helps not in this case. |
Hi all, |
Hi all,
after updating the syncstorage-rs container from 0.13.7 to 0.14.0 the container crashes.
The log is filled with this messages you see in the attached log.
FirefoxSync_RS_logs.txt
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: