Buildiso doesn't work in docker #323
Labels
No labels
Done
bug
buildiso
buildpkg
buildtree
critical
deployiso
duplicate
enhancement
help wanted
in progress
invalid
manjaro-chroot
note
old-not-relevant
optional
question
sonar
todo
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tools/manjaro-tools#323
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hello!
I am not experienced in CI/CD automatization, but I am trying to make auto build the iso in docker, which runs in CircleCI machine. I use machine executor in CircleCI to start docker in privileged mode, but buildiso still gives an error:
I use the next command to start the docker container:
I hope you will tell me the way to solve this problem. Maybe CircleCI not suitable for such purposes so what can I use for that?
Okay. I tried to use TravisCI. And it almost helped.
The problem #212 is repeated. I've not found the problem solution there and I've tried some ways to solve this by himself.
I found the similar issue and changed the docker run options:
And result of this command:

Also I observe errors during the build:

Anybody knows the solution?
Are you using the Manjaro Docker repo?
@mikeroyal I created docker image based on manjarolinux/base: Dockerfile.
Any updates to this? I am trying to do something very similiar but am running into the same error.
I noticed the container does log some
dmesgoutput as well, not sure if this is of use for debugging:Okay, I fixed the problem.
The issue stems from the fact that Docker itself uses an
overlayFSas its storage engine. It seems like you cannot mount anoverlayfilesystem from within anoverlayfilesystem which was causing the error. When I switched to VFS as the docker storage engine the error went away. Keep in mind that VFS is alot larger thanoverlay.The docker documentation on VFS and how to switch to it.
To any devs that might know how to fix this, it would be rather helpful. As (AFIK) almost all CI/CD pipelines will use
overlayas a filesystem. If I come across any fixes to get this working in GitHub actions I will report back.I had a question, where are the ISO changes made? This command is to generate the ISO automatically, I don't know where the changes will be.
/home/isobuilder/project-> this is inside the containerdemysteriismundi/manjarolinux-build-> This is the image that is on the hubWhere did you configure iso-profiles? (git clone https://gitlab.manjaro.org/profiles-and-settings/iso-profiles.git ~/iso-profiles)
Can you give me all the configuration you created? I'm trying to automate the iso creation of a distribution based on manjaro to be created inside the docker.
Closing stale issue