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

Update details on runtime environment #7

Open
brain-slug opened this issue Oct 8, 2021 · 1 comment · May be fixed by #8
Open

Update details on runtime environment #7

brain-slug opened this issue Oct 8, 2021 · 1 comment · May be fixed by #8

Comments

@brain-slug
Copy link

brain-slug commented Oct 8, 2021

Hi,

I tried to get it running using a Docker image based on ubuntu:20.04

FROM ubuntu:20.04

ENV SOURCE_GITLAB=git.mycompany.com
ENV TARGET_GITLAB=gitlab.com

RUN adduser migration

RUN apt-get update && \
    apt-get install git jq curl vim -y

COPY resources/migrate.sh /home/migration/
COPY resources/.secrets /home/migration/

RUN chown migration:migration /home/migration/migrate.sh && chmod +x /home/migration/migrate.sh
RUN chown migration:migration /home/migration/.secrets

USER migration

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.

  • Source GitLab Version: GitLab Enterprise Edition 14.3.1-ee
  • Target gitlab.com
  • curl --version 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 --version jq-1.6
  • bash --versionGNU 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?

@brain-slug
Copy link
Author

brain-slug commented Oct 8, 2021

Curious about the fact it worked using CURL_PARAMS="-v" I started playing with locale settings...

After some more debugging I found setting CURL_PARAMS="--raw" fixes the issue for me.

From curl man-pages

       --raw  (HTTP) When used, it disables all internal HTTP decoding
              of content or transfer encodings and instead makes them
              passed on unaltered, raw.

              Added in 7.16.2.

@brain-slug brain-slug linked a pull request Oct 11, 2021 that will close this issue
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

Successfully merging a pull request may close this issue.

1 participant