Why mfe theme didnt apply to mysite

Development Design
,
1

hi i install openedx with tutor and installed enabeled mfe and indigo theme for it but didnt apply to my site what should i do?

 tutor plugins list
NAME    STATUS          VERSION
indigo  ✅ enabled      19.0.0
mfe     ✅ enabled      19.0.0

when i open my site cant see any change

2

Default and Indigo themes looks quite similar.

3

What is your commands?.
tutor plugins enable indigo mfe
tutor plugins list
and you need follow this command.
tutor local launch

4

i do that but i cant see mfe on site

5

should i use tutor images build openedx?

6

Try to switch themes: tutor local do settheme default and tutor local do settheme indigo, if no errors about themes in tutor local logs --follow --tail=40 when you browsing your platform, then take a close look on what changes after theme switch.

By default there is no need to do tutor images build openedx. But if you see error messages in logs about themes when switching them, rebuilding openedx image may help.

7

Why is it that even though VPN and Proxy are secure, it seems that my docker command doesn’t pass and it gives 403 and I cant use tutor images build openedx

tutor images build openedx
⚠️  You are running Tutor as root. This is strongly not recommended. If you are doing this in order to access the Docker daemon, you should instead add your user to the 'docker' group. (see https://docs.docker.com/install/linux/linux-postinstall/#manage-docker-as-a-non-root-user)
Building image docker.io/overhangio/openedx:19.0.0-indigo
docker buildx build --tag=docker.io/overhangio/openedx:19.0.0-indigo --output=type=docker --cache-from=type=registry,ref=docker.io/overhangio/openedx:19.0.0-indigo-cache /root/.local/share/tutor/env/build/openedx
[+] Building 0.7s (2/2) FINISHED                                  docker-container:mybuilder
 => [internal] load build definition from Dockerfile                                    0.0s
 => => transferring dockerfile: 12.07kB                                                 0.0s
 => ERROR resolve image config for docker-image://docker.io/docker/dockerfile:1         0.7s
------
 > resolve image config for docker-image://docker.io/docker/dockerfile:1:
------
Dockerfile:1
--------------------
   1 | >>> # syntax=docker/dockerfile:1
   2 |     ###### Minimal image with base system requirements for most stages
   3 |     FROM docker.io/ubuntu:22.04 AS minimal
--------------------
ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1: unexpected status from HEAD request to https://registry-1.docker.io/v2/docker/dockerfile/manifests/1: 403 Forbidden
Error: Command failed with status 1: docker buildx build --tag=docker.io/overhangio/openedx:19.0.0-indigo --output=type=docker --cache-from=type=registry,ref=docker.io/overhangio/openedx:19.0.0-indigo-cache /root/.local/share/tutor/env/build/openedx
8

If you have restriction from docker, you can use mirrors Mirror | Docker Docs, for example this mirror Pull cached Docker Hub images  |  Artifact Registry documentation  |  Google Cloud. You can find more mirrors in thematic articles.

Or, maybe you faced with Usage and rate limits | Docker Docs … no, not 429 response code.