You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another thing is, after (re)creating the containers and running 'go run main.go' it has to download all dependencies again.
Had also to use a more recent version of Golang as it was complaining about snappy which required Golang v1.17 or above.
Hope you have any clue as I'm not really familiair with golang. Thanx in advance.
The text was updated successfully, but these errors were encountered:
Well, came a bit further. Gave it another try with the 'ancient' 1.11.2-version. Running gives an error with respect to arm64 and snappy which should be resolved in Golang 1.12, but after modifying a file that error was gone but then the crypto-thing complains about requireing 1.17.
root@7814d0d47a20:/go/src/github.com/Sierra1011/portwarden/cmd/portwarden# go run portwarden.go --passphrase 1234 --filename backup.encrypted
go build golang.org/x/crypto/pbkdf2: module requires Go 1.17
Note: forgot to mention. There are 2 Dockerfiles (Dockerfile and Dockerfile.Build). Using Dockerfile to build the image. Dockerfile.Build complains about dep ensure --vendor-only-command. Meanwhile dep is also deprecated.
As I'm missing the discussions-tab I'll use this one instead.
Wondering if you don't encounter any issues running your container(s) as I'm getting the following:
I have forked your repo and modified it to use arm64 instead of amd64 because I want to run it on a raspberry pi.
But running 'go run main.go' in the scheduler-container results in:
The same error when trying to make a backup:
Another thing is, after (re)creating the containers and running 'go run main.go' it has to download all dependencies again.
Had also to use a more recent version of Golang as it was complaining about snappy which required Golang v1.17 or above.
Hope you have any clue as I'm not really familiair with golang. Thanx in advance.
The text was updated successfully, but these errors were encountered: