search

jakeswenson / BitBetter

Modify bit warden to provide my own licensing for self hosting
510 stars 115 forks source link

Update / Restart Error "yaml.scanner" #131

Closed mrventerj closed 2 years ago

mrventerj commented 2 years ago

Hello Gents

Has something changed that I need to update?

When trying to update my BW to get a new cert I get the following:

bitwarden.sh version 1.47.1 Docker version 19.03.13, build 4484c46d9d docker-compose version 1.27.3, build 4092ae5d

ERROR: yaml.scanner.ScannerError: mapping values are not allowed here in "/home/LocalAdmin/bwdata/docker/docker-compose.override.yml", line 5, column 25 Bitwarden update completed!

And when trying to restart: ERROR: yaml.scanner.ScannerError: mapping values are not allowed here in "/home/LocalAdmin/bwdata/docker/docker-compose.override.yml", line 5, column 25 ERROR: yaml.scanner.ScannerError: mapping values are not allowed here in "/home/LocalAdmin/bwdata/docker/docker-compose.override.yml", line 5, column 25

mrventerj commented 2 years ago

The docker-compose.override.yml in the update script adds two colons after

image: bitbetter/api: and bitbetter/identity:

I removed the colons and chose not to recreate the override during the update prompts.

The update then goes a step further then before and attempts to pull the new files, I then get the following errors:

ERROR: for api pull access denied for bitbetter/api, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

ERROR: for identity pull access denied for bitbetter/identity, repository does not exist or may require 'docker login': denied: requested access to the resource is denied ERROR: pull access denied for bitbetter/identity, repository does not exist or may require 'docker login': denied: requested access to the resource is denied

This is my docker-compose.override.yml config if i choose not to override:

version: '3'

services: api: image: bitbetter/api

identity: image: bitbetter/identity

Any advice?

captainhook commented 2 years ago

Rebuild BitBetter and that should resolve this issue

mrventerj commented 2 years ago

@captainhook Thank you for the response.

I attempted the rebuild, by running the following- is this correct?: From the BitBetter directory, simply run:

./build.sh

I got the following error:

Determining projects to restore... All projects are up-to-date for restore. bitBetter -> /bitBetter/bin/Debug/netcoreapp3.1/bitBetter.dll bitBetter -> /bitBetter/bin/Debug/netcoreapp3.1/publish/ Sending build context to Docker daemon 2.85MB Step 1/6 : ARG BITWARDEN_TAG Step 2/6 : FROM ${BITWARDEN_TAG} invalid reference format Sending build context to Docker daemon 2.85MB Step 1/6 : ARG BITWARDEN_TAG Step 2/6 : FROM ${BITWARDEN_TAG} invalid reference format Error parsing reference: "bitbetter/api:" is not a valid repository/tag: invalid reference format Error parsing reference: "bitbetter/identity:" is not a valid repository/tag: invalid reference format

mrventerj commented 2 years ago

These are the refrences I have in my build file where the reference issue occurs:

docker build --no-cache --build-arg BITWARDEN_TAG=bitwarden/api:$BW_VERSION --label com.bitwarden.product="bitbetter" -t bitbetter/api "$DIR/src/bitBetter"$ docker build --no-cache --build-arg BITWARDEN_TAG=bitwarden/identity:$BW_VERSION --label com.bitwarden.product="bitbetter" -t bitbetter/identity "$DIR/src/$

mrventerj commented 2 years ago

@captainhook I saw my build.sh was still referring to an older framework 3. I replace my build.sh file with the latest one, I get the following errors now:

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:

**When I run the following it seems like it is installed?: sudo apt --installed list | grep "dotnet"

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

dotnet-apphost-pack-3.1/bionic,now 3.1.23-1 amd64 [installed,auto-removable] dotnet-host/bionic,now 6.0.3-1 amd64 [installed,auto-removable] dotnet-hostfxr-3.1/bionic,now 3.1.23-1 amd64 [installed,auto-removable] dotnet-runtime-deps-3.1/bionic,now 3.1.23-1 amd64 [installed,auto-removable] dotnet-targeting-pack-3.1/bionic,now 3.1.0-1 amd64 [installed,auto-removable]

mrventerj commented 2 years ago

Nothing worked, restored this BW VM to a week old backup, changed the BW server's Weekly backups to Daily backups as this was irreparable in my scope of limited technical ability, I even tried the workaround in this: https://github.com/jakeswenson/BitBetter/issues/115

@jakeswenson , @captainhook So I have a working BW now, but how do I go about updating BW now? ./update-bitwarden.sh is what caused the issue for me.

Ubuntu 18.04.5 LTS BW Version: Version 1.45.2 according to docker-override.yml.

mrventerj commented 2 years ago

Deleted the BitBetter folder, cloned in again, ran the build.sh, had to delete existing docker containers for some reason. (Parent images or something) Updated and working.

mrventerj commented 2 years ago

Thanks for the response, hope you get well. I somehow figured it out after trying a bunch of stray punches. The lesson learned: should have been running daily backups instead of weekly on my password server. Thanks for the efforts on this project to you and the team. @h44z *Saw the merge just now.