Now there may be some different between permissions, run dpkg-reconfigure sudo to fix it. If everything goes right, your sudoers file will be back and you will be able to use sudo as you were before. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.
Create a free Team What is Teams? Learn more. Asked 4 years, 9 months ago. Active 6 months ago. Viewed 21k times. Improve this question. Cassie Cassie 1 1 gold badge 2 2 silver badges 8 8 bronze badges. You still get the "No such file" error although the file is there? The permissions and ownership is also correct as you show it in your ls -l output. Can you try to reinstall the sudo package by running pkexec apt-get install --reinstall sudo?
Errors were encountered while processing — Cassie. You could try that, but it will likely also remove a bunch of other packages depending on sudo with it, which you would have to reinstall later as well. I also doubt that it would help with the error you describe. ByteCommander I was careless and I gave rights to sudoers. Add a comment. Active Oldest Votes.
After all, if you changed sudoers. However I'm curious of why the post script of the checkout action needs to know the ID of the docker image? I'm bumping into the same problem. So the failure probably happens before the container is even started. In addition, I suspect this has nothing to do with the checkout action even.
It's likely a problem with GitHub Actions themselves. Which makes it pretty hard to debug since it's closed source.. Yesterday I stumbled across this error using a BusyBox container and found this issue, today I took some time to debug it. The reason for this is that GitHub Actions are written in JavaScript, so in order for an action to run inside a container, Node.
The problem is that this build may not be compatible with the container. In my case, BusyBox doesn't have the required shared libraries. My armchair suggestion is that the Node. I've done a quick experiment that allows the action to run inside BusyBox, but I warn that no one under any circumstances should use it as a workaround.
After all, this PR 70 turned this action into an action called "JavaScript Actions", so we can use v1 to checkout the code without any extra hacks.
Hey smorimoto , using checkout v1 works for me! The reason v1 of the checkout action works is that it depends only on Bash. The source for v1 of the checkout action was not published, but it was Bash if I remember correctly. I'm getting similar error when running ARM architecture container on self-hosted runner with qemu :. Do I understand right that the checkout action, which is a javascript action, in this case is run inside of the container and since there is no nodejs present in the container it can't run the action?
Can you debug with this? ItsReddi yeah that sounds familiar. I created an upstream PR in that project, which got meged and confirmed to work now. I had the same issue in this sample trivial repo , but only in 32 bit containers, Alpine and Debian. Following smorimoto 's advice to use checkout v1 the issue went away. In the error case, with step debug logging, I get this :. I can now ssh between the machines using fixed NAT addresses.
All ports are open on forth. Before moving up to autofs make sure you can manually mount anything from the command line directly! Sign up to join this community.
The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 8 years, 3 months ago. Active 8 years, 3 months ago. Viewed 18k times. Improve this question.
Add a comment. Active Oldest Votes.
0コメント