Skip to content
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

Trying to port to arm64 but until now can't get it completely working #40

Open
pluim003 opened this issue Mar 20, 2023 · 2 comments
Open

Comments

@pluim003
Copy link

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:

../../core.go:130:20: invalid method expression archiver.Zip.Write (needs pointer receiver: (*archiver.Zip).Write)

The same error when trying to make a backup:

# github.com/Sierra1011/portwarden
../../core.go:130:20: invalid method expression archiver.Zip.Write (needs pointer receiver: (*archiver.Zip).Write)

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.

@pluim003
Copy link
Author

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

@pluim003
Copy link
Author

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.

Sierra1011 pushed a commit that referenced this issue Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant