missing squashfs support on ChromeOS

Bug #1973233 reported by Anthony Intravaia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Invalid
Undecided
Unassigned

Bug Description

the package complied and installed Jammy on chroot Crouton
the maybe why it will not start loop9 File system does not exist
do I need to make one?
it difficult to install software without snap running it want to run some adjustment can be made
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 20K 1 loop
loop1 7:1 0 14.7G 0 loop
└─encstateful 254:1 0 14.7G 0 dm /var/host/timezone
loop2 7:2 0 471.8M 1 loop
loop3 7:3 0 4K 1 loop
loop4 7:4 0 4K 1 loop
loop5 7:5 0 97M 1 loop
loop6 7:6 0 7.3M 1 loop
loop7 7:7 0 22M 1 loop
loop8 7:8 0 150M 1 loop
└─6CB3CF03D025531946DC8AC5581AFAC6EF973A8AAB1DABBB24A63111E5141B06 254:2 0 81.9M 1 dm
sda 8:0 1 183.3G 0 disk /var/host/media/removable/sd200
                                                                                             /
mmcblk0 179:0 0 58.2G 0 disk
├─mmcblk0p1 179:1 0 50.1G 0 part /home/coc/Downloads
├─mmcblk0p2 179:2 0 32M 0 part
├─mmcblk0p3 179:3 0 4G 0 part
├─mmcblk0p4 179:4 0 32M 0 part
├─mmcblk0p5 179:5 0 4G 0 part
├─mmcblk0p6 179:6 0 512B 0 part
├─mmcblk0p7 179:7 0 512B 0 part
├─mmcblk0p8 179:8 0 16M 0 part
├─mmcblk0p9 179:9 0 512B 0 part
├─mmcblk0p10 179:10 0 512B 0 part
├─mmcblk0p11 179:11 0 512B 0 part
└─mmcblk0p12 179:12 0 64M 0 part
mmcblk0boot0 179:16 0 4M 1 disk
mmcblk0boot1 179:32 0 4M 1 disk
zram0 253:0 0 3.7G 0 disk [SWAP]

Tags: chroot jammy
Revision history for this message
Anthony Intravaia (otostone) wrote :
Revision history for this message
Anthony Intravaia (otostone) wrote :

better log error pic

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

ChromeOS does not support squashfs apparently. Please ask for support in the forum: https://forum.snapcraft.io

summary: - Snapd files system ? loop9?
+ missing squashfs support on ChromeOS
Changed in snapd:
status: New → Invalid
Revision history for this message
Anthony Intravaia (otostone) wrote :

in developer mode it supports Title:
  missing squashfs

On Thu, May 12, 2022 at 11:15 PM Maciej Borzecki <email address hidden>
wrote:

> ChromeOS does not support squashfs apparently. Please ask for support in
> the forum: https://forum.snapcraft.io
>
> ** Summary changed:
>
> - Snapd files system ? loop9?
> + missing squashfs support on ChromeOS
>
> ** Changed in: snapd
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1973233
>
> Title:
> missing squashfs support on ChromeOS
>
> Status in snapd:
> Invalid
>
> Bug description:
> the package complied and installed Jammy on chroot Crouton
> the maybe why it will not start loop9 File system does not exist
> do I need to make one?
> it difficult to install software without snap running it want to run
> some adjustment can be made
> NAME
> MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
> loop0
> 7:0 0 20K 1 loop
> loop1
> 7:1 0 14.7G 0 loop
> └─encstateful
> 254:1 0 14.7G 0 dm /var/host/timezone
> loop2
> 7:2 0 471.8M 1 loop
> loop3
> 7:3 0 4K 1 loop
> loop4
> 7:4 0 4K 1 loop
> loop5
> 7:5 0 97M 1 loop
> loop6
> 7:6 0 7.3M 1 loop
> loop7
> 7:7 0 22M 1 loop
> loop8
> 7:8 0 150M 1 loop
> └─6CB3CF03D025531946DC8AC5581AFAC6EF973A8AAB1DABBB24A63111E5141B06
> 254:2 0 81.9M 1 dm
> sda
> 8:0 1 183.3G 0 disk /var/host/media/removable/sd200
>
> /
> mmcblk0
> 179:0 0 58.2G 0 disk
> ├─mmcblk0p1
> 179:1 0 50.1G 0 part /home/coc/Downloads
> ├─mmcblk0p2
> 179:2 0 32M 0 part
> ├─mmcblk0p3
> 179:3 0 4G 0 part
> ├─mmcblk0p4
> 179:4 0 32M 0 part
> ├─mmcblk0p5
> 179:5 0 4G 0 part
> ├─mmcblk0p6
> 179:6 0 512B 0 part
> ├─mmcblk0p7
> 179:7 0 512B 0 part
> ├─mmcblk0p8
> 179:8 0 16M 0 part
> ├─mmcblk0p9
> 179:9 0 512B 0 part
> ├─mmcblk0p10
> 179:10 0 512B 0 part
> ├─mmcblk0p11
> 179:11 0 512B 0 part
> └─mmcblk0p12
> 179:12 0 64M 0 part
> mmcblk0boot0
> 179:16 0 4M 1 disk
> mmcblk0boot1
> 179:32 0 4M 1 disk
> zram0
> 253:0 0 3.7G 0 disk [SWAP]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snapd/+bug/1973233/+subscriptions
>
>

--
Anthony
6508800038

Revision history for this message
Anthony Intravaia (otostone) wrote : Re: [Bug 1973233] Re: missing squashfs support on ChromeOS

the linux OS does if snap need a loop9 device why does it not create one

On Thu, May 12, 2022 at 11:36 PM Tony Rome <email address hidden> wrote:

> in developer mode it supports Title:
> missing squashfs
>
>
> On Thu, May 12, 2022 at 11:15 PM Maciej Borzecki <
> <email address hidden>> wrote:
>
>> ChromeOS does not support squashfs apparently. Please ask for support in
>> the forum: https://forum.snapcraft.io
>>
>> ** Summary changed:
>>
>> - Snapd files system ? loop9?
>> + missing squashfs support on ChromeOS
>>
>> ** Changed in: snapd
>> Status: New => Invalid
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1973233
>>
>> Title:
>> missing squashfs support on ChromeOS
>>
>> Status in snapd:
>> Invalid
>>
>> Bug description:
>> the package complied and installed Jammy on chroot Crouton
>> the maybe why it will not start loop9 File system does not exist
>> do I need to make one?
>> it difficult to install software without snap running it want to run
>> some adjustment can be made
>> NAME
>> MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
>> loop0
>> 7:0 0 20K 1 loop
>> loop1
>> 7:1 0 14.7G 0 loop
>> └─encstateful
>> 254:1 0 14.7G 0 dm /var/host/timezone
>> loop2
>> 7:2 0 471.8M 1 loop
>> loop3
>> 7:3 0 4K 1 loop
>> loop4
>> 7:4 0 4K 1 loop
>> loop5
>> 7:5 0 97M 1 loop
>> loop6
>> 7:6 0 7.3M 1 loop
>> loop7
>> 7:7 0 22M 1 loop
>> loop8
>> 7:8 0 150M 1 loop
>> └─6CB3CF03D025531946DC8AC5581AFAC6EF973A8AAB1DABBB24A63111E5141B06
>> 254:2 0 81.9M 1 dm
>> sda
>> 8:0 1 183.3G 0 disk /var/host/media/removable/sd200
>>
>> /
>> mmcblk0
>> 179:0 0 58.2G 0 disk
>> ├─mmcblk0p1
>> 179:1 0 50.1G 0 part /home/coc/Downloads
>> ├─mmcblk0p2
>> 179:2 0 32M 0 part
>> ├─mmcblk0p3
>> 179:3 0 4G 0 part
>> ├─mmcblk0p4
>> 179:4 0 32M 0 part
>> ├─mmcblk0p5
>> 179:5 0 4G 0 part
>> ├─mmcblk0p6
>> 179:6 0 512B 0 part
>> ├─mmcblk0p7
>> 179:7 0 512B 0 part
>> ├─mmcblk0p8
>> 179:8 0 16M 0 part
>> ├─mmcblk0p9
>> 179:9 0 512B 0 part
>> ├─mmcblk0p10
>> 179:10 0 512B 0 part
>> ├─mmcblk0p11
>> 179:11 0 512B 0 part
>> └─mmcblk0p12
>> 179:12 0 64M 0 part
>> mmcblk0boot0
>> 179:16 0 4M 1 disk
>> mmcblk0boot1
>> 179:32 0 4M 1 disk
>> zram0
>> 253:0 0 3.7G 0 disk [SWAP]
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/snapd/+bug/1973233/+subscriptions
>>
>>
>
> --
> Anthony
> 6508800038
>

--
Anthony
6508800038

Revision history for this message
Anthony Intravaia (otostone) wrote :

hello i have installed Package: squashfs-tools if snap need a loop9 device
with a sqashFS how much bytes does it need

On Thu, May 12, 2022 at 11:15 PM Maciej Borzecki <email address hidden>
wrote:

> ChromeOS does not support squashfs apparently. Please ask for support in
> the forum: https://forum.snapcraft.io
>
> ** Summary changed:
>
> - Snapd files system ? loop9?
> + missing squashfs support on ChromeOS
>
> ** Changed in: snapd
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1973233
>
> Title:
> missing squashfs support on ChromeOS
>
> Status in snapd:
> Invalid
>
> Bug description:
> the package complied and installed Jammy on chroot Crouton
> the maybe why it will not start loop9 File system does not exist
> do I need to make one?
> it difficult to install software without snap running it want to run
> some adjustment can be made
> NAME
> MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
> loop0
> 7:0 0 20K 1 loop
> loop1
> 7:1 0 14.7G 0 loop
> └─encstateful
> 254:1 0 14.7G 0 dm /var/host/timezone
> loop2
> 7:2 0 471.8M 1 loop
> loop3
> 7:3 0 4K 1 loop
> loop4
> 7:4 0 4K 1 loop
> loop5
> 7:5 0 97M 1 loop
> loop6
> 7:6 0 7.3M 1 loop
> loop7
> 7:7 0 22M 1 loop
> loop8
> 7:8 0 150M 1 loop
> └─6CB3CF03D025531946DC8AC5581AFAC6EF973A8AAB1DABBB24A63111E5141B06
> 254:2 0 81.9M 1 dm
> sda
> 8:0 1 183.3G 0 disk /var/host/media/removable/sd200
>
> /
> mmcblk0
> 179:0 0 58.2G 0 disk
> ├─mmcblk0p1
> 179:1 0 50.1G 0 part /home/coc/Downloads
> ├─mmcblk0p2
> 179:2 0 32M 0 part
> ├─mmcblk0p3
> 179:3 0 4G 0 part
> ├─mmcblk0p4
> 179:4 0 32M 0 part
> ├─mmcblk0p5
> 179:5 0 4G 0 part
> ├─mmcblk0p6
> 179:6 0 512B 0 part
> ├─mmcblk0p7
> 179:7 0 512B 0 part
> ├─mmcblk0p8
> 179:8 0 16M 0 part
> ├─mmcblk0p9
> 179:9 0 512B 0 part
> ├─mmcblk0p10
> 179:10 0 512B 0 part
> ├─mmcblk0p11
> 179:11 0 512B 0 part
> └─mmcblk0p12
> 179:12 0 64M 0 part
> mmcblk0boot0
> 179:16 0 4M 1 disk
> mmcblk0boot1
> 179:32 0 4M 1 disk
> zram0
> 253:0 0 3.7G 0 disk [SWAP]
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snapd/+bug/1973233/+subscriptions
>
>

--
Anthony
6508800038

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

Please use the forum link I provided earlier. I think there were some people who tried using snaps on ChromeOS with limited success.

Revision history for this message
Anthony Intravaia (otostone) wrote :

thank you
Jammy is running on chroot , and was config with debootstrap

I got some ideas from Snap about changing the jammy kernel

chromeOS is the OS that the chroot runs in Developer mode, so memory is open to install what you wish

It has some issues systemd and tcp are not the issue some adjustments can be made
Snapd when you compile their package via go it ask you to write to submit bug reports here so i did

really the whole idea is team work

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.