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

Docker Run Failed #44

Open
slr1997 opened this issue Feb 25, 2025 · 3 comments
Open

Docker Run Failed #44

slr1997 opened this issue Feb 25, 2025 · 3 comments

Comments

@slr1997
Copy link

slr1997 commented Feb 25, 2025

after step 2, I use docker run swelancer, then it shows this:

Unknown ruby interpreter version (do not know how to handle): >=3.3.4.
Starting Xvfb on display :99...
Starting bspwm window manager...
Starting x11vnc server...
Starting NoVNC...
Starting Pusher-Fake service...

PLAY [localhost] ***************************************************************

TASK [Gathering Facts] *********************************************************
[WARNING]: Platform linux on host localhost is using the discovered Python
interpreter at /opt/conda/bin/python3.12, but future installation of another
Python interpreter could change the meaning of that path. See
https://docs.ansible.com/ansible-
core/2.18/reference_appendices/interpreter_discovery.html for more information.
ok: [localhost]

TASK [Ensure ISSUE_ID environment variable is set] *****************************
ok: [localhost] => {
    "changed": false,
    "msg": "All assertions passed"
}

TASK [Verify the flow file does not contain PII or unnecessary information] ****
changed: [localhost]

TASK [Create a new log directory for the ISSUE_ID] *****************************
changed: [localhost]

TASK [Create a new attempts directory for the ISSUE_ID] ************************
changed: [localhost]

TASK [Generate empty certs store] **********************************************
changed: [localhost]

TASK [Generate CA authority using mkcert] **************************************
changed: [localhost]

TASK [Modify /etc/hosts file to include dev.new.expensify.com] *****************
changed: [localhost]

TASK [Get the commit ID for the issue] *****************************************
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "ISSUE_ID=\ncat /app/tests/issues/$ISSUE_ID/commit_id.txt\n", "delta": "0:00:00.005996", "end": "2025-02-25 06:22:42.025876", "msg": "non-zero return code", "rc": 1, "start": "2025-02-25 06:22:42.019880", "stderr": "cat: /app/tests/issues//commit_id.txt: No such file or directory", "stderr_lines": ["cat: /app/tests/issues//commit_id.txt: No such file or directory"], "stdout": "", "stdout_lines": []}

PLAY RECAP *********************************************************************
localhost                  : ok=8    changed=6    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

for the network problem, I downloaded the expansify.zip first and changed the dockerfile as:

RUN apt-get update && apt-get install -y unzip
COPY expensify.zip /tmp/
RUN ls -la /tmp/expensify.zip
RUN mkdir -p /app/expensify
RUN unzip -l /tmp/expensify.zip
RUN unzip /tmp/expensify.zip -d /tmp
RUN ls -la /tmp
RUN mv /tmp/App-main/* /app/expensify/ 
#|| mv /tmp/Expensify* /app/expensify || ls -la /tmp/*
RUN rm /tmp/expensify.zip

Am I doing anything wrong?

@andy-wong-andy-wong
Copy link

andy-wong-andy-wong commented Feb 25, 2025

Also noticed this. I added another check to check if ISSUE_ID was an empty string.
I wonder if these steps are required for running expensify or mitproxy. Can we run the setup scripts without having the ISSUE_ID set?

I ran the package like the following:
docker run ISSUE_ID=1 swelancer

@geeker-smallwhite
Copy link

I had the same problem

@ShaneTian
Copy link

I had the same problem~

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

4 participants