T16:04:07.1344097Z Can't find any online and idle self-hosted runner in current repository's account/organization that matches the required labels: 'ubuntu-latest' T16:04:07.1344029Z Can't find any online and idle self-hosted runner in current repository that matches the required labels: 'ubuntu-latest' Script: 'cd /var/When running the script I get the following raw log: T16:04:06.7573174Z #Starting: Request a runner to run this job Git config -local user.email config -local user.name "GitHub Action" My workflows/main.yml file looks like the following: name: CD My bash-script to start the deployment process looks like this: #!/bin/sh $ cat configĪlso, anytime you make a git repository as sharedrepository for group using the above command, it will also set the nyNonFastforwards to true automatically as shown above.I am trying to setup github actions to deploy my application. User.name=John above will solve the insufficient permission issue permanently.Īfter you set the sharedrepository, if you view the config file under your git repository, you’ll notice that the value of sharedrepository parameter is set to 2 (which is group) as shown below. Now, if you view the git config as shown below, you’ll see the “core.sharedrepository” parameter set to group. The “group” in the above command should be typed exactly as it is. Use the above above command exactly as shown without changing anything. Note: In the above command, don’t replace the keyword “group” with your groupname (for example: git). To convert a bare repository to shared repository, do the following: git config core.sharedRepository group The above command displays the configuration values from the “config” file that is located under your git repository. So, this particular repository (i.e myproj is not setup as shared repository). User.name=John the above output, we don’t see a parameter called “core.sharedrepository”. To verify whether your repository is already setup for group sharing, do the following git config -l option inside your git repository that has the problem. If it is not setup as shared repository, you’ll see the above “insufficient permission on objects directory” issue starts to show-up again. In this case, the git repository (for example: myproj) is not setup as shared repository for groups. So, apart from fixing the permission error as explained above, we also need to fix the underlying problem. chmod -R 777 objectsīut, even after doing the above, the same problem might return again, and you may have to do the above chgrp and chmod whenever the problem occurs. Instead execute the above chgrp and chmod command. But, as you can imagine, it is not a good idea to do 777.
You may be tempted to execute the following on your objects directory, which will solve the problem that you are having. This will make sure any new directory created under objects folder will make the group name from the objects folder which is owned by git group.
The “s” option in the “g+rws” is to set the setuid bit on the objects folder.Change the “git” in the above chgrp command to whatever group where all your developers belong to. Make sure all your users who need access to git are part of the git group.Also make sure the user and group has read and write permission to the directory. To solve this problem, execute the following, which will set the group to git (or whatever group where all the users belongs to. Set the Appropriate Permissions on Objects Directory In this particular case, when john is trying to do ‘git push’, he is getting the above error because some of the directories under the objects folder of git repository are owned by lisa as shown ls -l objects If you don’t see the objects directory directly under your repository folder, then look under the. Because of this error, it failed to push some refs as shown above.įirst, cd to the git repository which is having this issue. ! master -> master (n/a (unpacker error))Įrror: failed to push some refs to also shows that the git unpack failed with unpack-objects abnormal exit. objectsĮrror: unpack failed: unpack-objects abnormal exit Writing objects: 100% (4/4), 388 bytes, | 0 bytes/s, done.Įrror: insufficient permission for adding an object to repository database.
objects directory under your repository.Īpart from the obvious permission issue, there is also another underlying problem that needs to be addressed, which is explained in this tutorial. The following git push error indicates that it doesn’t have enough permission for adding a new object to the. This error typically happens when multiple users are working on a particular git repository. Sometimes when you do a git push, you might get the following permission error message.
0 kommentar(er)
