-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update details on runtime environment #7
Comments
Curious about the fact it worked using After some more debugging I found setting From curl man-pages
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I tried to get it running using a Docker image based on ubuntu:20.04
I verified .secrets file is read correctly (after fixing EOL issues) adding echo.
Still I am seeing multiple curl errors like
curl: (3) URL using bad/illegal format or missing URL
.GitLab Enterprise Edition 14.3.1-ee
curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3 Release-Date: 2020-01-08
jq-1.6
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
Fun fact if I add
CURL_PARAMS="-v"
to migrate.sh it works...Could you please share runtime specific settings (bash_profile/locale/encoding etc) which have proofed to be working?
The text was updated successfully, but these errors were encountered: