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
When running docker-compose run boulder ./test.sh (or anything) when $GOPATH isn't set, I get this cryptic error:
ERROR: Cannot create container for service boulder: create .: volume name is too short, names should be at least two alphanumeric characters
As of Go 1.8, the default $GOPATH is $HOME/go so requiring $GOPATH to be explicitly set will be increasingly confusing to people. This was something that tripped me up when I first started working on Boulder.
The text was updated successfully, but these errors were encountered:
Good catch, thanks. And this is something that I think has caught a number of people.
This may be tricky to implement, however. Right now we rely on these two lines in docker-compose.yml:
volumes:
- $GOPATH:/go/
This doesn't really support if/else statements. And I think the plan is to actually deprecate variable interpolation in future Docker versions. So we need to figure out what the best practice is for mounting a path that's usually in someone's homedir into a docker volume (with docker compose).
Removes the reliance on `$GOPATH` being set in order to use `docker-compose`. Also removes
a few unnecessary commands from the `Dockerfile` that were no longer doing anything. If you
get weird errors along the lines of `oci runtime error: cannot chdir to ...` you will need to
`docker-compose rm; docker-compose build; docker-compose up` to fix them.
Fixes#2660.
When running
docker-compose run boulder ./test.sh
(or anything) when $GOPATH isn't set, I get this cryptic error:As of Go 1.8, the default
$GOPATH
is$HOME/go
so requiring$GOPATH
to be explicitly set will be increasingly confusing to people. This was something that tripped me up when I first started working on Boulder.The text was updated successfully, but these errors were encountered: