Unable to locate lsb_release #688
Comments
|
Hello @mnboos. Thank you for your report. Could you please provide a public repository to reproduce the issue? |
|
Hello @dmitry-shibanov Unfortunately not right now. We internally self-host Gitea and none of the infrastructure is publicly available. However, I can provide you with all the necessary information, if this helps. |
|
Thank you for your response @mnboos. Do you use cache ? Could you please run this command: |
I don't think so, my runners config file is the following, I just changed the log level to cat config.yml
# Example configuration file, it's safe to copy this as the default config file without any modification.
log:
# The level of logging, can be trace, debug, info, warn, error, fatal
level: debug
runner:
# Where to store the registration result.
file: .runner
# Execute how many tasks concurrently at the same time.
capacity: 1
# Extra environment variables to run jobs.
envs:
A_TEST_ENV_NAME_1: a_test_env_value_1
A_TEST_ENV_NAME_2: a_test_env_value_2
# Extra environment variables to run jobs from a file.
# It will be ignored if it's empty or the file doesn't exist.
env_file: .env
# The timeout for a job to be finished.
# Please note that the Gitea instance also has a timeout (3h by default) for the job.
# So the job could be stopped by the Gitea instance if it's timeout is shorter than this.
timeout: 3h
# Whether skip verifying the TLS certificate of the Gitea instance.
insecure: false
# The timeout for fetching the job from the Gitea instance.
fetch_timeout: 5s
# The interval for fetching the job from the Gitea instance.
fetch_interval: 2s
# The labels of a runner are used to determine which jobs the runner can run, and how to run them.
# Like: ["macos-arm64:host", "ubuntu-latest:docker://node:16-bullseye", "ubuntu-22.04:docker://node:16-bullseye"]
# If it's empty when registering, it will ask for inputting labels.
# If it's empty when execute `deamon`, will use labels in `.runner` file.
labels: []
cache:
# Enable cache server to use actions/cache.
enabled: false
# The directory to store the cache data.
# If it's empty, the cache data will be stored in $HOME/.cache/actcache.
dir: ""
# The host of the cache server.
# It's not for the address to listen, but the address to connect from job containers.
# So 0.0.0.0 is a bad choice, leave it empty to detect automatically.
host: ""
# The port of the cache server.
# 0 means to use a random available port.
port: 0
container:
# Specifies the network to which the container will connect.
# Could be host, bridge or the name of a custom network.
# If it's empty, act_runner will create a network automatically.
network: ""
# Whether to use privileged mode or not when launching task containers (privileged mode is required for Docker-in-Docker).
privileged: false
# And other options to be used when the container is started (eg, --add-host=my.gitea.url:host-gateway).
options:
# The parent directory of a job's working directory.
# If it's empty, /workspace will be used.
workdir_parent:
|
|
Hello @mnboos. Do you use docker image ? Could you please try to reinstall lsb-release and add it to the PATH ? Besides, does the setup-python action fail and during python execution ? |
No, it's just an Ubuntu VM.
Sure: $ sudo apt-get reinstall lsb-release
[sudo] password for adminmbo20:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 10.6 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 lsb-release all 11.1.0ubuntu2 [10.6 kB]
Fetched 10.6 kB in 0s (165 kB/s)
(Reading database ... 131871 files and directories currently installed.)
Preparing to unpack .../lsb-release_11.1.0ubuntu2_all.deb ...
Unpacking lsb-release (11.1.0ubuntu2) over (11.1.0ubuntu2) ...
Setting up lsb-release (11.1.0ubuntu2) ...
Processing triggers for man-db (2.9.1-1) ...
It already is: $ which lsb_release
/usr/bin/lsb_release
$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
setup-python fails. It does not come to execution of python.
|
|
Hello @mnboos. Thank you for your response. Could you please try to use the approach from this comment ? If it does not work could you please try to use this snippet to check that python works in your self-hosted runner. - name: Download python 3.10
run: |
wget https://github.com/actions/python-versions/releases/download/3.10.12-5200619051/python-3.10.12-linux-20.04-x64.tar.gz -O ${{ runner.temp }}/python-3.10.12-linux-20.04-x64.tar.gz
mkdir ${{ runner.temp }}/python-3.10.12-linux-20.04-x64
tar -xzvf ${{ runner.temp }}/python-3.10.12-linux-20.04-x64.tar.gz -C ${{ runner.temp }}/python-3.10.12-linux-20.04-x64
- name: Run script
run: |
echo "run script"
bash setup.sh
working-directory: ${{ runner.temp }}/python-3.10.12-linux-20.04-x64
- run: echo "/opt/hostedtoolcache/Python/3.10.12/x64/" >> $GITHUB_PATH
- run: python --version |
|
Hi @dmitry-shibanov Thanks for your support. I had to make a slight adjustment, i.e. adding - name: Run script
run: |
echo "run script"
export LD_LIBRARY_PATH=/tmp/python-3.10.12-linux-20.04-x64/lib
bash setup.sh
working-directory: ${{ runner.temp }}/python-3.10.12-linux-20.04-x64Now also this step works: - name: Set up Python 3.10
uses: https://github.com/actions/setup-python@v4
with:
python-version: "3.10"
token: ${{ secrets.GH_TOKEN }}
cache: "poetry" |
|
Hello @mnboos. For now I'm going to close the issue because we could not reproduce it. If you have any concerns feel free ping us. |
|
@dmitry-shibanov This is still happening. I am using the |
|
Hello @adamgranthendry. Do you use self-hosted agent ? Do you use cache input ? What permissions do you have for lsb-release? |
|
|
@dmitry-shibanov Correction: this appears fixed with The error remains when using |
Description:
The job fails with the following error:
Action version:
4
Platform:
Runner type:
Tools version:
3.10Repro steps:
The following workflow:
Expected behavior:
Should workflow should complete successfully.
Actual behavior:
The text was updated successfully, but these errors were encountered: