-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
/var/lib/apt/list permission problem building under WSL2 and Docker Desktop #5798
Comments
Jira ticket: AR-1885 |
Don't know if this was ever tested. We tested on several different machines with default WSL2 installation. It worked even on ARM based Windows 11. Can this be disabled somehow? |
This scenario is untested, I was not aware Docker Desktop would infiltrate wsl2. Try to avoid using docker: |
When I installed docker desktop a while ago, it defaulted to using WSL2 as a backend. See their docs if you're curious. The only docker related logs in the I'm unable to build without docker at this time since my WSL2 OS (focal) isn't supported to build armbian natively. |
My guess is this Docker Desktop WSL2 backend is messing up the Docker volumes. Otherwise yeah use WSL2 jammy sans-docker. |
I did not use Docker Desktop, I'm using WSL2 Ubuntu 22.04 under Win10 and installing docker on Ubuntu: sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin With this Build is working |
WSL2 jammy is the only supported build host on Windows. |
Just Solution from https://askubuntu.com/questions/1096930/sudo-apt-update-error-release-file-is-not-yet-valid |
What happened?
All builds that I've tried from main fail due to broken apt sources. I get the following output:
How to reproduce?
I'm running the command from within WSL2 on Windows 11 with Docker Desktop running. I ran the following build command:
Branch
main (main development branch)
On which host OS are you observing this problem?
Other
Relevant log URL
https://paste.next.armbian.com/iquculijin
Code of Conduct
The text was updated successfully, but these errors were encountered: