This has moved to:
How can I remove Jetbrains toolbox once installed ?
thanks @j0rge, thought I could have done it with the app manager or something…
All good!
On a fresh bluefin install, there is no devmode recipe. Instead, I found devmode-on and devmode-off. After running devmode-on I get:
Pulling manifest: ostree-unverified-image:oci:/var/ublue-os/image
error: Creating importer: Failed to invoke skopeo proxy method OpenImage: remote error: lstat /var/ublue-os: no such file or directory
error: Recipe `devmode-on` failed with exit code 1
What am I doing wrong?
Looks like you’re on a fresh install, this part in the status shows that you’re still on the image from initial installation: ostree-unverified-image:oci:/var/ublue-os/image
Do a just update, that will rebase you to a signed image and then reboot to apply all the updates. Then the command will be there. Sorry about the installer jank, hopefully we won’t need to deal with this for much longer. 
1 Like
I just tried to rebase to bluefin from silverblue. No overlayed packages (I already did reset and cleaned everything), but I get the following error:
fdr@fdr-framework:~$ sudo rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-framework:39
Place your left index finger on the fingerprint reader
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-framework:39
error: Preparing import: Fetching manifest: containers-policy.json specifies a default of `insecureAcceptAnything`; refusing usage
I’m out of lock trying to reason about this one 
Any ideas?
Edit: some extra info: /etc/containers/policy.json is not edited, so it has the default values from /usr/etc
You can’t rebase to a signed image from Fedora (they don’t have our signing key), so you need to rebase to an unsigned image first, follow these instructions:
2 Likes
With the recent Debian kernel drama, I’m all the more looking forward to the day when I can use bluefin-dx-nvidia as my daily driver!
3 Likes
Why is not all the commands listen when you just type just? For example there is no mention of ˙just devmode˙, and i think there is no mention of it in the docs, either unless I missed it.
just is outputting the commands here:
You can check out this section in the just docs to make sure your ~/.justfile has the right imports in it.
If you’re not getting results it’s likely that file isn’t set up right. However just upstream has merged in the import feature into the stable branch, which will require some adjustments on our part, so heads up on that: fix: Use import for just by KyleGospo · Pull Request #179 · ublue-os/config · GitHub
The devmode section is at the top of the document.
I’m getting this error when trying to use a dev container in vscode on a fresh installation
[1519 ms] Command failed: docker ps -q -a --filter label=vsc.devcontainer.volume.name=anaconda --filter label=vsc.devcontainer.volume.folder=anaconda
[1558 ms] Exit code 1
[1563 ms] Command failed: node /root/.vscode-remote-containers/dist/dev-containers-cli-0.327.0/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /workspaces/anaconda --id-label vsc.devcontainer.volume.name=anaconda --id-label vsc.devcontainer.volume.folder=anaconda --log-level debug --log-format json --mount-workspace-git-root
[1564 ms] Exit code 1
Thanks for trying it! How fresh is your installation? We just landed the devcontainer support last night. Which container are you trying to launch?
I found a couple of potential issues with the benchmark code:
git clone https://github.com/aime-team/pytorch-benchmarks.git
cd pytorch-benchmarks
python3 main.py --num_gpus 2 --compile --model bert-large-uncased --data_name squad --global_batch_size 24
First, the code assumes two GPUs (--num_gpus 2).
Second, when I ran the code on my RTX A4500, it ran out of memory. I had about 15GB of the 20GB free at the time.
Both of these could limit who can successfully run the benchmark.
1 Like
I had just installed it a few minutes before posting, but I’ll try again! It was just the default python container, but all of them were giving me this error.
1 Like
Wow, this is a new world for me. First learning about immutable os , than i found this.
Lot of things to read 
1 Like
FYI, running just by itself isn’t printing the available commands as the discussion above indicates it should. Instead, I get the message error: Justfile contains no default recipe.
My ~/.justfile just imports /usr/share/ublue-os/justfile, and that in turn imports /usr/share/ublue-os/just/00-default.just, which contains a recipe called _default that does what j0rge descibes above, but that recipe doesn’t get executed as the default recipe in the installed version of just. After reviewing the just docs, it’s ambiguous to me whether this is correct behavior or a bug… the docs say that the default recipe is the first receipe, and bluefin’s _default is the first after processing imports, but perhaps the just dev meant the first recipe in the main justfile.
Edit: Oh, I see that there’s also a ujust command that behaves as described… this issue was discussed in this post. That makes sense, but given that the Bluefin announcment blog post uses plain just in its examples, this could continue confusing new users, at least until more getting started documentation is written. FWIW, I’d vote for sticking with the plain just command to avoid confusion, and just moving the default recipe into ~/.justfile if needed.
1 Like
I’ll edit the blog post to fix it up, sorry we’re getting a bunch of new users during the just transition and it’s taking a while to fix up the docs.
1 Like
Do you expect any issues to appear when running both docker containers and podman containers at the same time? For example, vscode open and attached to some work in a docker devcontainer, plus a prompt terminal attached to a distrobox (podman) wolfi container.
I note that the CoreOS docs advise against it:
Fedora CoreOS Frequently Asked Questions :: Fedora Docs (fedoraproject.org)
I’m wondering how relatable the problems are here.
@siosm pinged us and let us know but I can’t seem to find the github issue where we discussed that.
Here’s a bunch of related back story though: Recommend docker as the default for vscode/devcontainers · Issue #726 · ublue-os/bluefin · GitHub
I run with this setup all the time and haven’t had issues since we switched but I do keep an eye out for it. So far so good unless someone has had a bad experience that wants to share?
1 Like