octoprint / custopizer Goto Github PK

Hello

I've made 2 test:

1. Using the https://github.com/guysoft/OctoPi/releases/download/1.0.0/octopi-bullseye-armhf-lite-1.0.0.zip and it work fine !

2. Using the https://github.com/guysoft/OctoPi/releases/download/1.0.0/octopi-bullseye-arm64-lite-1.0.0.zip but i get an error :

Building on non-ARM device a armv7l system, using qemu-arm-static
qemu-arm-static: /bin/bash: Invalid ELF image for this architecture
Error: Process completed with exit code 255.

Hey, very useful package, team!

I'm wondering what part of this stack might need to change to build for an arm6 architecture? (We want to be able to build Rpi Zero images)

Here's what I attempted: I changed the EDITBASE_ARCH to armv6l, and running the run command did produce an output.img, but custom scripts didn't execute.

The common.sh file should be removed - sadly my skills with chaning docker images are not that good :/

not sure why, but custopizer keeps failing at the end with

+ apt-get clean
+ apt-get autoremove -y
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
/CustoPiZer/workspace /
Unmounting /CustoPiZer/workspace/mount/var/cache/apt...
Unmounting /CustoPiZer/workspace/mount/dev/pts...
umount: /CustoPiZer/workspace/mount/dev/pts: target is busy.

I've done it 3 times and this happens before to rebuilds the fs to shrink it so the img is large, I haven't tested to see if it's usable at this stage. Any ideas, should there be a force or a wait on this for pts to finish up?

Was attempting to do some tweaks to my github actions and ran across this error during build...

Running /CustoPiZer/start_chroot_script in chroot...
Building on non-ARM device a armv7l system, using qemu-arm-static
+ set -e
+ export LC_ALL=C
+ LC_ALL=C
+ source /common.sh
+ install_cleanup_trap
+ set -e
+ trap cleanup SIGINT SIGTERM
+ '[' raspbian == ubuntu ']'
+ '[' -n '' ']'
+ '[' -n '' ']'
+ apt-get update
Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 http://archive.raspberrypi.org/debian buster/main armhf Packages [378 kB]
Reading package lists...
E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
Error: Process completed with exit code 100.

I'm assuming this is related to debian release change upstream from raspbian based on this article.

https://www.raspberrypi.org/forums/viewtopic.php?p=1905664

Hello. I'm fairly new to Linux. Running ubuntu 20.04 and trying to build a custom raspberry pi image, starting from the latest octopi image. I have configured everything I want in my custom image and when I run the docker command I get the following error that I'm note sure how to work around:

update-binfmts: warning: qemu-arm already enabled in kernel.
mount: /proc/sys/fs/binfmt_misc: binfmt_misc already mounted on /proc/sys/fs/binfmt_misc.
Running /CustoPiZer/start_chroot_script in chroot...
Building on non-ARM device a armv7l system, using qemu-arm-static
qemu-arm-static: /bin/bash: Invalid ELF image for this architecture

Maybe a support ask / documentation ask: is it possible to specify the file name of the input image, instead of assuming input.img?

Maybe to make it easier for the noobs like me add this to the readme:

If you are having problems getting the container to connect to the internet for updates etc. then run with:
--dns 8.8.8.8

Adding my own config options seems to cause issues if the file is created under windows with carriage return on the line end.
The config parses correctly but when the value for f.e. resizing the partition is passed to dd it gets fed a carriage return.

....
EDITBASE_IMAGE_ENLARGEROOT=2000
EDITBASE_IMAGE_RESIZEROOT=200
EDITBASE_MOUNT_PATH=/CustoPiZer/workspace/mount
EDITBASE_PYPI_INDEX=
EDITBASE_ROOT_PARTITION=2
EDITBASE_WORKSPACE=/CustoPiZer/workspace
================================================================
/CustoPiZer/workspace /
 MB to partition 2 of /CustoPiZer/workspace/output.img
dd: invalid number: '2000\r'

the doc to inspect an image is not working out of the box, as docker is expecting a path and not a file. further the -v is missing.

this is working for me:
docker run -it --rm --privileged -v /path/to/image_folder:/img ghcr.io/octoprint/custopizer:latest /CustoPiZer/enter_image /img/image.img