#Can't find my ISO after using the new generate_secureblue_iso.sh script.

1 messages Β· Page 1 of 1 (latest)

stray gust
#

I try out the new generate_secureblue_iso.sh script, but can't find my ISO after generation.

I can't neiter find bluefin-nvidia-userns-hardened-latest.iso or deploy.iso

Those are the last lines of the output with the new image generator:

-chmod 0444 base-39/oci-layout
<ler/container/base-39/index.json base-39/index.json
-chmod 0444 base-39/index.json
-end
implantisomd5 build/deploy.iso
Inserting md5sum into iso image...
md5 = eeccc56af75ee70457c006d8ae9eec7d
Inserting fragment md5sums into iso image...
fragmd5 = 88ee7bca371e7373385aef8868d8bbba56828a6c2953a588d738a37e95fa
frags = 20
Setting supported flag to 0
chmod ugo=r build/deploy.iso
cd build/ && sha256sum deploy.iso > deploy.iso-CHECKSUM```

That's with the old isogenerator for reference and that works with correctly formatted image. (`bluefin-nvidia-userns-hardened-latest.iso` in my case):

============================
implantisomd5 /isogenerator/output/bluefin-nvidia-userns-hardened-latest.iso
Inserting md5sum into iso image...
md5 = 94a506e9ed030191777d7773ed28dd0a
Inserting fragment md5sums into iso image...
fragmd5 = f55778cf2efea49399138be512a39d6795ba39682efd4196894bdf3237c1
frags = 20
Setting supported flag to 0

devout bluff
#

Ah, yeah this is a bug. Please create a github issue

stray gust
#

Can you do it please? I have no account. 😟

devout bluff
#

It's easy to make one πŸ˜„

stray gust
#

Yeah i know but i don't want it. πŸ˜‚

devout bluff
#

so you want me to put in effort to fix something but you don't want to put in a tiny amount of effort? πŸ™‚

stray gust
#

Ok i will make an account. Where do i file the issue? At github for secureblue or the github from the maintainer of the new image builder?

stray gust
#

It it okay so?

devout bluff
#

looks good, thanks

stray gust
#

πŸ‘

devout bluff
#

@stray gust question just out of curiosity, why are you generating a new iso if you're already on secureblue?

stray gust
#

As a backup installation media, and also for MY curiosity to test your script. I like testing new stuff. πŸ˜‚

stray gust
#

Ok, i did just test the image generator, and it make an iso, but it has the name "deploy.iso" and not the right name for the image! Also the file is only 2,7 GB in size, the old one was about 5 GB in size, is that correct so?

stray gust
#

Ok I tried that deploy.iso in a virtual machine. It is installing just the Base Image, and it is for a server! The script will not use the right image arguments! Therefore it grabs no image!

#

Now i know why the Image is so small in size!

devout bluff
#

looking at it

devout bluff
#

@stray gust can you try again

stray gust
#

Ok, the image creation is working and it is pulling the right image now, but the name of the image is still deploy.iso not the real imagename like for example bluefin-nvidia-userns-hardened-latest.iso.

devout bluff
#

one sec

#

@stray gust try now

stray gust
#

Ok, now i can't find the generated ISO and also no CHECKSUM File in the work folder! 😒

stray gust
#
-chmod 0444 bluefin-nvidia-userns-hardened-latest/oci-layout
<on bluefin-nvidia-userns-hardened-latest/index.json
-chmod 0444 bluefin-nvidia-userns-hardened-latest/index.json
-end
implantisomd5 bluefin-nvidia-userns-hardened.iso
Inserting md5sum into iso image...
md5 = d9edb3e2a68c9b9f988ee0fdcad4b9f9
Inserting fragment md5sums into iso image...
fragmd5 = 32ad9e24db6723f16924fb3863b62d26d5d4df24abcfbf1b8ccec264effe
frags = 20
Setting supported flag to 0
chmod ugo=r bluefin-nvidia-userns-hardened.iso
cd ./ && sha256sum bluefin-nvidia-userns-hardened.iso > bluefin-nvidia-userns-hardened.iso-CHECKSUM

These are the last outputs.

stray gust
#

I think it is missing the ISO_PATH= attribute.

stray gust
#

I can also commit changes

#

Got something like this in my mind: ISO_PATH=file://$(dirname "$0")/$image_name.iso, but does not work.

devout bluff
stray gust
#

Ok, when it is working as intended i make a pull request.

devout bluff
#

@stray gust i think i have it working

#

im just gonna add a mv to the end to change the name

#

since the iso generation container doesn't want to do it

#

@stray gust should work now

stray gust
#

Yeah, it creates now the iso in my home directory, not where the script is.

devout bluff
stray gust
#

No, from ~./Downloads

#

Testing that: command="sudo podman run --rm --privileged --volume .:/build-container-installer/build ghcr.io/jasonn3/build-container-installer:latest IMAGE_REPO=ghcr.io/secureblue IMAGE_NAME=$image_name ISO_NAME=$image_name.iso ISO_PATH="$(dirname "$0")/$iso_name" VERSION=40 IMAGE_TAG=latest" right now.

#

I want that the ISO is created in the same folder as the script. Seems really complicated with the image generator. Renaming the files is also not a good idea, because of the CHECKSUM file, that is still deploy.iso in there as the name!

stray gust
#

It's working good. Tested so many times and the newest version of the script is the only one that's working good.

devout bluff