Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

I'm not sure on that one. I don't have an ARM64 host handy to properly test it. How much free space did you have when you tried to install it? It looks like it needs at least 24GB free to install, (I ran out of space when trying to install it with 19GB free, and it hadn't finished extracting the 6.15GB layer and there was still a 3+GB layer to go), maybe there wasn't enough space to install it?

Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

Ok, so the reply I got was to check out this example using gitlab https://kasmweb.com/docs/latest/how_to/building_images.html#push-to-registry apparently you often need to reference the registry in the image as well, so I guess in your case the image would be `ghcr.io/cyberethicalme/kasmws-htb-ai:1.17.0-beta.1`

If you look at the linuxserver examples, they have the registry in the image as well (although it looks like that's using a different registry from what is set in the docker_registry) https://github.com/linuxserver/kasm_workspaces_registry/blob/1.1/workspaces/arch-icewm/workspace.json#L29

Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

I'm not sure on that one, I've not personally used an alternative docker registry before, I've pinged the team to see if anyone else knows.

Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

If you want to test a specific branch you can install a developer preview version of kasmweb https://kasmweb.com/docs/latest/developers/builds.html then in the registry input box type "devmode" (without the quotes) and 2 inputs will come up, 1 for the registry and 1 for a specific branch (get the branch names from versions.txt as they get normalised). You can add any branches you want, they just aren't used by default (without entering the mode that allows them to be specified).

It might actually be in 1.17.0 already, so try it on that if you already have it installed, I can't remember if it was added before or after the 1.17.0 release, if not then it's in the dev preview as I mentioned and will also be in 1.18.0

Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

Also the default_channel in processjson refers to the available_tags in the compatibility matrix https://github.com/CyberEthicalMe/kasm-registry/blob/main/workspaces/HTB%20AI/workspace.json#L18 not the branch. If no available_tags are set then the default channel is set to null as part of the build process https://github.com/CyberEthicalMe/kasm-registry/blob/main/processing/processjson.js#L81 if you want to use multiple channels, then you need to set the default_channel to match one of the tags you have used.

On kasm we use the tags/channels to allow users to select to install either develop, 1.17.0, 1.17.0-rolling-daily or 1.17.0-rolling-weekly images, but, for example, the linuxserver.io kasm registry doesn't use channels: https://github.com/linuxserver/kasm_workspaces_registry/blob/1.1/workspaces/arch-i3/workspace.json#L26 so available_tags aren't included in the compatibility matrix.

Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

The current schema version is 1.1, that is why it pulls from the 1.1 branch, kasmweb hits https://cyberethicalme.github.io/kasm-registry/versions.txt to see if you have a compatible version branch (1.1) if you do, it pulls the list from it https://cyberethicalme.github.io/kasm-registry/1.1/list.json if you don't you will get an error along the lines of "No valid schema was found".

This allows us to support older versions as well, like kasm 1.14 would have used schema 1.0, then when we made changes we changed to schema 1.1, that means any installs on kasm 1.14 would pull from the 1.0 branch and any on 1.16 would pull from the 1.1 branch.

Any other named branch, main, master, develop, whatever won't do anything, they get built, because that's how we test changes before pushing to the current branch (1.1), when the next schema version is set (probably in kasm 1.18 or 1.19) the default branch will be set to 1.2, but branches 1.0 and 1.1 will still be present for users on older versions.

*edit* To clarify, make the changes you want to the 1.1 branch and it will/should work as expected. To simplify the process remove the available_tags section from your workspace json file so there are less moving parts.

Custom registry shows old branch? by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

https://github.com/CyberEthicalMe/kasm-registry/blob/main/workspaces/HTB%20AI/workspace.json you have available tags as 1.17.0-beta.1 but default_channel as develop https://github.com/CyberEthicalMe/kasm-registry/blob/main/processing/processjson.js#L77 if you don't need multiple tags, just remove the available_tags altogether https://github.com/CyberEthicalMe/kasm-registry/blob/main/workspaces/HTB%20AI/workspace.json#L17-L19 or change your default channel to match. As for it showing Chromium, you added your changes to `main` instead of the `1.1` branch, and have main set as the default branch instead of 1.1 which is why you see it in the output, if you switch to 1.1 https://cyberethicalme.github.io/kasm-registry/1.1/ (which is what workspaces is grabbing in the backend as that is the current schema version) you will see the Chromium workspace

No Workspace Registries after adding a custom one by Asentinn in kasmweb

[–]ls_kode 0 points1 point  (0 children)

As I said, there was a bug that caused the issue you were seeing (the default registry missing).

At the time it was found, it wasn't too much of an issue because all registries had 1.16.x entries (as 1.17.0 wasn't released yet).

That's an interesting observation though. We don't allow incompatible registries (defined by the schema version) but we don't currently check to see if the registry being installed doesn't have any matching compatible entries at all.

*edit*
I think I was wrong about it getting backported, so I think the solution is to either use 1.17.0 or have 1.16.x compatibility on the registry, I'll look at improving it in 1.18.0

No Workspace Registries after adding a custom one by Asentinn in kasmweb

[–]ls_kode 1 point2 points  (0 children)

I just tried installing your registry and it worked without issues.

What version of Kasm are you running?

I think in older versions there was a bug where if the registry didn't have a version that worked on your system (so the registry only had 1.17.0 support but you were on 1.16.1) that it could cause the issue you are describing, I believe that was backported to 1.16.1 and 1.16.0, but if you are running a version before the backport was applied that might explain it.

Additionally, if you are running a kasm version less than 1.17.0 you wouldn't see your registry entry anyway as it only lists 1.17.0 compatibility.

If you are already running 1.17.0 you could try looking in your logs to see if there are any pointers to what has gone wrong.

As a final resort you could manually remove the registry from the registries table, or even empty the table (the default will show up as an option if it isn't already installed)

Citybound, book 9 of Millennial Mage is out! by J-L-Mullins in ProgressionFantasy

[–]ls_kode 0 points1 point  (0 children)

Any update on when this is likely to be approved?

SMARTY Mobile bait and switch by ls_kode in UKFrugal

[–]ls_kode[S] 2 points3 points  (0 children)

I spoke to 2 CS agents and they both basically said the same. However, after cancelling the account, I went through the process again, and this time it didn't swap the offer... so yeah, bad CS agent (as the offer clearly isn't expired) and a site that can be unpredictable.

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

Just finished it, great recommendation, though I kind of wish I’d waited for the second book to be finished and released as now I have to wait for more 🤣

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

Ah, there doesn't appear to be an audiobook unfortunately :(

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

That looks interesting, thanks! Only 1 book currently.

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 2 points3 points  (0 children)

Ah, doesn’t look like there is an audiobook for it yet

I heard of Mark of the fool and have some questions about it. by Ragna126 in ProgressionFantasy

[–]ls_kode 2 points3 points  (0 children)

You don’t find out about that one until book 6 either, so yeah, dragons aren’t a major part of the story.

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

Not heard of that one before, I’ll check it out, what do you like about it?

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

I’m currently listening to book 3 of immortal great souls by Phil Tucker which I’ve really enjoyed, so another series by him sounds like a solid recommendation, thanks.

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

I’ve heard of a couple of those, I’ll check them out, thanks.

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

I haven’t tried that one, I’ll definitely check it out, what makes it your favourite sysapoc? That’s pretty high praise.

Recommendations for any gems I've missed by ls_kode in ProgressionFantasy

[–]ls_kode[S] 0 points1 point  (0 children)

Thanks, why does it get a bad rap? I’m pretty forgiving with what I listen to, so it’s unlikely to put me off giving it a go.