Customizing chromium settings

Technical Support
, , ,
1

Our manufacturing team noticed that the chromium kiosk was underlining misspelled words, which is probably not desirable in our application (though not a must change setting either.)

I found that if I launched in browser mode instead of kiosk mode, I could go into the settings and disable the spell check, but there doesn’t seem to be any way to pass a command line argument to change anything.

Since those settings would only live within the life of the container, I am not 100% sure the best way to save those settings, and get them to persist across multiple machines over multiple docker instances. I was able to locate the settings file, at /home/torizon/.config/chromium/Default/Preferences inside the container, but copying just this file, or the entire directory using the dockerfile is giving errors about not being able to read the lock files in the directory due to permissions, and usually crashing the container.

I am not sure a convenient way to work around that. If we just have to accept the spell check its not the end of the world, but it would be nice to be able to edit those settings if there was a convenient way to do so.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! Thank you for your detailed description of the issue.

You can disable spell check in Chromium in kiosk mode by passing the --disable-spell-checking flag directly to Chromium when starting your container. This is much simpler and more reliable than trying to persist or manipulate Chromium’s settings files, which—as you’ve observed—can lead to permission and lock file issues.

To disable spell checking, use this approach:

If you’re launching Chromium via a docker run command:

docker run -d --rm --name=chromium \
  -v /tmp:/tmp -v /dev/dri:/dev/dri \
  -v /var/run/dbus:/var/run/dbus --device-cgroup-rule='c 226:* rmw' \
  --security-opt seccomp=unconfined --shm-size 256mb \
  torizon/chromium-am62:$CT_TAG_CHROMIUM \
  --virtual-keyboard --disable-spell-checking https://www.toradex.com

(reference)

Or, in a Docker Compose file you can add it to the command:

services:
  kiosk:
    image: torizon/chromium
    command: --virtual-keyboard --disable-spell-checking --window-mode https://www.toradex.com/
    # [other options, volumes, etc.]

(reference)

This method ensures the spell checker is disabled every time your kiosk container starts up, with no need to modify internal preference files or manage permission issues.

If you need any further assistance on the configuration, feel free to ask!

Best regards, Toradex AI Assistant.

3

Hey @dTanks,

Was the AI suggestion able to help you turn off the spell check underline?

-Eric

4

Eric,

As far as I can tell, the AI completely made up that flag.

–disable-spell-checking does nothing when I try it.

https://peter.sh/experiments/chromium-command-line-switches/
Seems to list the flags that could be used, and nothing is listed there for spell checking

There is nothing in the shell script used to launch chromium that handles that flag either, unless there is a new version of that somewhere.

5

Hey @dTanks,

From our documents we link an unofficial list of flags that can be passed to chromium. While this list is extensive, it doesn’t cover everything, this list is also referenced in the chromium documents . From looking at the chromium Projects, it does look like there is a SpellChecker Object method.

  • Eric
6

HI @eric.tx

I am not sure I understand your answer. It seems that you linked the same list that I did, but I can’t find anything within the list for disabling spell checking. All my searches have indicated I have to do so thru the chrome settings, and I don’t know how to persist this setting between docker containers.

If there is an undocumented flag for turning it off, that would be great, but I am not sure how to find that.

7

Hey @dTanks,

I’m not sure what you mean between containers,between different instances of the same container? You would have to have the docker image already contain the changes which produces the container to have it persist through different container runs.

-Eric

8

@eric.tx

When I try to copy the settings file to the container, it crashes, as I mentioned in my original post.

I was able to locate the settings file, at /home/torizon/.config/chromium/Default/Preferences inside the container, but copying just this file, or the entire directory using the dockerfile is giving errors about not being able to read the lock files in the directory due to permissions, and usually crashing the container.

From what I understand, chromium is checking if files exist, and erroring out if the configuration isn’t as it expects. Its also creating symlinks to other files within the container, and this seems to be part of the crashing issue when I try to copy these files into the container.

Anyway, it seems like no convenient solution exists to set the chromium settings, and as far as I can tell the command line arguments are a bust as well, so I am just going to assume this isn’t possible to achieve.

9

Hey @dTanks,

If you have a config file/directory on the module that the container needs access to, you have to give it permission to do to, either via bind mount or volume.