You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One essential feature of a distro is to install the software it offers.
That can be handled via commands when creating a Docker image.
However, in the cross architecture case, the host providing the environment would typically not be able to run the package manager made for the foreign architecture.
A solution would be to install a specific package using the machine to cpu into. That could be accepted to happen at container runtime, even though it'd be ephemeral. Now that raises another problem: package managers typically extract to some temporary directory, lock their database, move the files from the temporary directory and then commit to the darabase to finally unlock it. The 9p protocol used here, though, does not offer moving files, and locking needs some investigation. hugelgupf/p9#52 should have fixed the lock
Note: I may have been using a somewhat older cpu binary.
I need to recheck again with a current build of the cpu command.
The text was updated successfully, but these errors were encountered:
orangecms
changed the title
Missing lock and move
Missing move, check on lock
Mar 30, 2023
In the README, we describe a cool hack - using a Docker image as a rootfs, enabling the cpu namespace to provide a whole distro:
https://github.com/u-root/cpu#cpu-and-docker
One essential feature of a distro is to install the software it offers.
That can be handled via commands when creating a Docker image.
However, in the cross architecture case, the host providing the environment would typically not be able to run the package manager made for the foreign architecture.
A solution would be to install a specific package using the machine to cpu into. That could be accepted to happen at container runtime, even though it'd be ephemeral. Now that raises another problem: package managers typically extract to some temporary directory, lock their database, move the files from the temporary directory and then commit to the darabase to finally unlock it. The 9p protocol used here, though, does not offer moving files, and locking needs some investigation.
hugelgupf/p9#52 should have fixed the lock
Note: I may have been using a somewhat older
cpu
binary.I need to recheck again with a current build of the
cpu
command.The text was updated successfully, but these errors were encountered: