Restic/builder still relies on vendor directory

Development
1

As far as I can tell https://github.com/restic/builder still relies on go modules being present in the vendor directory:

$ docker run --rm \
    --volume "$(pwd):/restic" \
    --volume "$(pwd)/output:/output" \
    restic/builder
build github.com/spf13/pflag: cannot load github.com/spf13/pflag: open /restic/vendor/github.com/spf13/pflag: no such file or directory

Does anybody know how to create reproducible builds with restic builder?

2

Ive been having the same issue. Any progress?

3

Hey, thanks for the hint! That docker container is only being used to build the official binaries. Before the next release, I’ll update the file so that it works again.

What are you trying to do? Building restic from source can (and should) be done without the container…

1 Like
4

I tried to build the official binaries to avoid using the Go version on my local machine.

5

Gotcha, thanks for the explanation

1 Like
6

Any idea when that “next release” might be? :wink:

7

What type of timeframe are you in need of? It will be done when it’s done, there’s still some stuff to do and we’re not keen to give a specific timeframe. We’d rather focus on doing the work and release when we feel that it is ready and time to make a release. Is there any specific reason you are asking?

8

Thats fine. I was just curious.

9

First, great work on getting the new release out.

I went to make a reproducible build for v0.10.0 and think I’ve seeing a similar issue when using https://github.com/restic/builder. I’m getting the following error message: build flag -mod=vendor only valid when using modules