Enhancement: Support Remote Containers extension #149

New Issue

Closed

opened 2026-10-05 02:29:31 +02:00 by adam · 23 comments

adam commented 2026-10-05 02:29:31 +02:00

Owner

Copy link

Copy source

It would be great if the Remote Containers extension ( https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers ) could be supported, please.

I use Fedora Silverblue, VS Code runs on a Flatpak and Hugo runs on a separate Toolbx container (Docker-compatible). At the moment the Front Matter extension does not load any content.

Thanks in advance for considering this.

It would be great if the Remote Containers extension ( https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers ) could be supported, please. I use Fedora Silverblue, VS Code runs on a Flatpak and Hugo runs on a separate Toolbx container (Docker-compatible). At the moment the Front Matter extension does not load any content. Thanks in advance for considering this. <!-- github-sync-id:1062497828 -->

adam closed this issue 2026-10-05 02:29:32 +02:00

adam commented 2026-10-05 02:29:32 +02:00

Author

Owner

Copy link

Copy source

Haven't used the Remote Containers extension. Where does the content live? Is it still on your file system?

Haven't used the Remote Containers extension. Where does the content live? Is it still on your file system? <!-- github-comment-id:978012111 -->

adam commented 2026-10-05 02:29:33 +02:00

Author

Owner

Copy link

Copy source

In the case of toolbx yes, as the home directory is available to the container. What is not available is the /usr, /etc partitions, so Front Matter is not able to find Hugo.

In the case of toolbx yes, as the home directory is available to the container. What is not available is the /usr, /etc partitions, so Front Matter is not able to find Hugo. <!-- github-comment-id:978091408 -->

adam commented 2026-10-05 02:29:34 +02:00

Author

Owner

Copy link

Copy source

I've been experimenting with the Remote Containers extension. What I did, was in my hugo project, I've added a .devcontainer folder with the devcontainer.json and dockerfile.

When starting up the project, load it from the container. I installed the Front Matter extension.

Opening the dashboard, loads all my markdown files without an issue.

The extension looks for files in its current workspace. Do your files live outside the VS Code workspace? If so, how do you connect your content folder? If you could guide me through it, I can also test it on my end, and hopefully find a solution.

I've been experimenting with the Remote Containers extension. What I did, was in my hugo project, I've added a `.devcontainer` folder with the `devcontainer.json` and `dockerfile`. When starting up the project, load it from the container. I installed the `Front Matter` extension.  Opening the dashboard, loads all my markdown files without an issue. <img width="1888" alt="Screenshot 2021-11-24 at 20 48 37" src="https://user-images.githubusercontent.com/2900833/143304687-c0a390a9-8336-47ec-8e9b-daa9ea4ff47b.png"> The extension looks for files in its current workspace. Do your files live outside the VS Code workspace? If so, how do you connect your content folder? If you could guide me through it, I can also test it on my end, and hopefully find a solution. <!-- github-comment-id:978177427 -->

adam commented 2026-10-05 02:29:34 +02:00

Author

Owner

Copy link

Copy source

Thanks for looking into this, I appreciate your time.

I run Fedora Silverblue (35). In Silverblue the base operating system is immutable and gets upgrade on an atomic way. GUI applications are packaged in Flatpaks (which are essentially containers) and development environment run on (pet) containers using Toolbx (which is a Podman wrapper).

In my set up I run VS Code as a Flatpak (which has access to $HOME), my blog is stored a directory in $HOME, and hugo is installed on a Toolbx container called "blog" that has access to $HOME.

If you wanted to replicate my environment (in a VM) on top of the standard Silverblue setup you would need to install VS Code from https://flathub.org/apps/details/com.visualstudio.code , follow the instructions at https://github.com/owtaylor/toolbox-vscode to enable the integration of VS Code and Toolbx, create a Toolbx and install hugo on it.

These are the steps I followed this morning:

1. Entered the toolbx: toolbox enter blog
2. Navigated to the folder that contains the blog.
3. Launched VS code from within the toolbox code . &
4. Opened the blog as a workspace.
5. Deleted the Front Matter files are re-initialised the project.
6. The dashboard shows empty for Markdown entries. The media folder has files though.

This is how it looks like:

This is the container configuration file from the Remote Containers extension:

{
  // Support requested in https://github.com/microsoft/vscode-remote-release/issues/4053.
  // "name": "Toolbox blog",
  "remoteUser": "${localEnv:USER}",
  "remoteEnv": {
    "PATH": "/var/home/jorgeml/.local/bin:/var/home/jorgeml/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
},
"workspaceFolder": "/var/home/jorgeml/Workspace/blog/jorgeml",
"extensions": [
	"eliostruyf.vscode-front-matter"
]
}

It's also possible to start the container, open the VS Code Flatpak (in the host OS) and then attach VS Code to the running container ( like shown in https://code.visualstudio.com/docs/remote/attach-container ).

Please let me know if this helps.

Thanks for looking into this, I appreciate your time. I run Fedora Silverblue (35). In Silverblue the base operating system is immutable and gets upgrade on an atomic way. GUI applications are packaged in Flatpaks (which are essentially containers) and development environment run on (pet) containers using Toolbx (which is a Podman wrapper). In my set up I run VS Code as a Flatpak (which has access to $HOME), my blog is stored a directory in $HOME, and hugo is installed on a Toolbx container called "blog" that has access to $HOME. If you wanted to replicate my environment (in a VM) on top of the standard Silverblue setup you would need to install VS Code from https://flathub.org/apps/details/com.visualstudio.code , follow the instructions at https://github.com/owtaylor/toolbox-vscode to enable the integration of VS Code and Toolbx, create a Toolbx and install hugo on it. These are the steps I followed this morning: 1. Entered the toolbx: `toolbox enter blog` 2. Navigated to the folder that contains the blog. 3. Launched VS code from within the toolbox `code . &` 4. Opened the blog as a workspace. 5. Deleted the Front Matter files are re-initialised the project. 6. The dashboard shows empty for Markdown entries. The media folder has files though. This is how it looks like:  This is the container configuration file from the Remote Containers extension: ``` { // Support requested in https://github.com/microsoft/vscode-remote-release/issues/4053. // "name": "Toolbox blog", "remoteUser": "${localEnv:USER}", "remoteEnv": { "PATH": "/var/home/jorgeml/.local/bin:/var/home/jorgeml/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" }, "workspaceFolder": "/var/home/jorgeml/Workspace/blog/jorgeml", "extensions": [ "eliostruyf.vscode-front-matter" ] } ``` It's also possible to start the container, open the VS Code Flatpak (in the host OS) and then attach VS Code to the running container ( like shown in https://code.visualstudio.com/docs/remote/attach-container ). Please let me know if this helps. <!-- github-comment-id:979009769 -->

adam commented 2026-10-05 02:29:35 +02:00

Author

Owner

Copy link

Copy source

Just one more quick check, if you right-click on a file in the explorer panel from VS Code, and click on copy path, which path do you get?

Just one more quick check, if you right-click on a file in the explorer panel from VS Code, and click on `copy path`, which path do you get? <!-- github-comment-id:979015464 -->

adam commented 2026-10-05 02:29:36 +02:00

Author

Owner

Copy link

Copy source

/var/home/jorgeml/Workspace/blog/jorgeml/content/posts

`/var/home/jorgeml/Workspace/blog/jorgeml/content/posts` <!-- github-comment-id:979022168 -->

adam commented 2026-10-05 02:29:36 +02:00

Author

Owner

Copy link

Copy source

frontmatter.json

{
  "$schema": "https://frontmatter.codes/frontmatter.schema.json",
  "frontMatter.framework.id": "hugo",
  "frontMatter.content.pageFolders": [
    {
      "title": "posts",
      "path": "[[workspace]]/content/posts"
    }
  ]
}

frontmatter.json ``` { "$schema": "https://frontmatter.codes/frontmatter.schema.json", "frontMatter.framework.id": "hugo", "frontMatter.content.pageFolders": [ { "title": "posts", "path": "[[workspace]]/content/posts" } ] } ``` <!-- github-comment-id:979023790 -->

adam commented 2026-10-05 02:29:37 +02:00

Author

Owner

Copy link

Copy source

Thanks for the details @jorgeml. The path was what I was hoping for, but that doesn't clarify yet why the extension doesn't find the files.

I have created a new #190 diagnostic output. It will be available in a couple of minutes in the BETA version of the extension. Would you be able to give it a try?

First uninstall the main version, second install the Front Matter BETA version. Nothing will be lost during the process. Once installed, can you execute the Front Matter: Diagnostics command? It should give some details about the project, workspace, and folders to process. Hoping to see an issue in the paths.

Important

: Make sure it is version 5.7.1503166 which is installed. It might take a bit of time before you see it in VS Code.

Thanks for the details @jorgeml. The path was what I was hoping for, but that doesn't clarify yet why the extension doesn't find the files. I have created a new #190 diagnostic output. It will be available in a couple of minutes in the BETA version of the extension. Would you be able to give it a try? First uninstall the main version, second install the `Front Matter BETA` version. Nothing will be lost during the process. Once installed, can you execute the `Front Matter: Diagnostics` command? It should give some details about the project, workspace, and folders to process. Hoping to see an issue in the paths. > **Important**: Make sure it is version `5.7.1503166` which is installed. It might take a bit of time before you see it in VS Code. <!-- github-comment-id:979053564 -->

adam commented 2026-10-05 02:29:38 +02:00

Author

Owner

Copy link

Copy source

Installed the extension and opened the workspace:

# Project name

jorgeml

# Folders



# Workspace folder

/var/home/jorgeml/Workspace/blog/jorgeml

# Folders to search files

Installed the extension and opened the workspace: ``` # Project name jorgeml # Folders # Workspace folder /var/home/jorgeml/Workspace/blog/jorgeml # Folders to search files ``` <!-- github-comment-id:979090206 -->

adam commented 2026-10-05 02:29:38 +02:00

Author

Owner

Copy link

Copy source

Oh, interesting, it is the folders which you aren't receiving. Do you have a frontMatter.content.pageFolders setting configuration in the settings.json file?

Oh, interesting, it is the folders which you aren't receiving. Do you have a `frontMatter.content.pageFolders` setting configuration in the `settings.json` file? <!-- github-comment-id:979092150 -->

adam commented 2026-10-05 02:29:39 +02:00

Author

Owner

Copy link

Copy source

Right, this was weird... I couldn't see the buttons to open the dashboard so I used the command palette to initialise the project, then I registered the content folder and the I could access the dashboard. Still empty though.

# Project name

jorgeml

# Folders

- posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts"

# Workspace folder

/var/home/jorgeml/Workspace/blog/jorgeml

# Folders to search files

- content/posts/**/*.md

Right, this was weird... I couldn't see the buttons to open the dashboard so I used the command palette to initialise the project, then I registered the content folder and the I could access the dashboard. Still empty though. ``` # Project name jorgeml # Folders - posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts" # Workspace folder /var/home/jorgeml/Workspace/blog/jorgeml # Folders to search files - content/posts/**/*.md ``` <!-- github-comment-id:979093926 -->

adam commented 2026-10-05 02:29:40 +02:00

Author

Owner

Copy link

Copy source

Ok, based on the post's path and the path you gave me before, it seems to be correct. I'll add the file retrieval count as well to the diagnostics.

Ok, based on the post's path and the path you gave me before, it seems to be correct. I'll add the file retrieval count as well to the diagnostics. <!-- github-comment-id:979096166 -->

adam commented 2026-10-05 02:29:40 +02:00

Author

Owner

Copy link

Copy source

New beta version is building at the moment and available in a couple of minutes.

This should include the number of files it finds in the folder.

# Project name

web-eliostruyf-hugo

# Folders

- Pages: "/Users/eliostruyf/blog/web-eliostruyf-hugo/content"
- Blog posts: "/Users/eliostruyf/blog/web-eliostruyf-hugo/content/posts"
- projects: "/Users/eliostruyf/blog/web-eliostruyf-hugo/content/projects"

# Workspace folder

/Users/eliostruyf/blog/web-eliostruyf-hugo

# Folders to search files

- Project start length: 7 | Search in: "content/*.*" | mdFiles: 0 | mdxFiles: 0
- Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 430 | mdxFiles: 0
- Project start length: 16 | Search in: "content/projects/**/*.*" | mdFiles: 1 | mdxFiles: 0

New beta version is building at the moment and available in a couple of minutes. This should include the number of files it finds in the folder. ```markdown # Project name web-eliostruyf-hugo # Folders - Pages: "/Users/eliostruyf/blog/web-eliostruyf-hugo/content" - Blog posts: "/Users/eliostruyf/blog/web-eliostruyf-hugo/content/posts" - projects: "/Users/eliostruyf/blog/web-eliostruyf-hugo/content/projects" # Workspace folder /Users/eliostruyf/blog/web-eliostruyf-hugo # Folders to search files - Project start length: 7 | Search in: "content/*.*" | mdFiles: 0 | mdxFiles: 0 - Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 430 | mdxFiles: 0 - Project start length: 16 | Search in: "content/projects/**/*.*" | mdFiles: 1 | mdxFiles: 0 ``` <!-- github-comment-id:979104754 -->

adam commented 2026-10-05 02:29:41 +02:00

Author

Owner

Copy link

Copy source

# Project name

jorgeml

# Folders

- posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts"

# Workspace folder

/var/home/jorgeml/Workspace/blog/jorgeml

# Folders to search files

- Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 0 | mdxFiles: 0

``` # Project name jorgeml # Folders - posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts" # Workspace folder /var/home/jorgeml/Workspace/blog/jorgeml # Folders to search files - Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 0 | mdxFiles: 0 ``` <!-- github-comment-id:979120329 -->

adam commented 2026-10-05 02:29:42 +02:00

Author

Owner

Copy link

Copy source

Changing the settings to look at content instead of posts doesn't look better:

# Project name

jorgeml

# Folders

- posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/"

# Workspace folder

/var/home/jorgeml/Workspace/blog/jorgeml

# Folders to search files

- Project start length: 8 | Search in: "content/**/*.*" | mdFiles: 0 | mdxFiles: 0

Changing the settings to look at content instead of posts doesn't look better: ``` # Project name jorgeml # Folders - posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/" # Workspace folder /var/home/jorgeml/Workspace/blog/jorgeml # Folders to search files - Project start length: 8 | Search in: "content/**/*.*" | mdFiles: 0 | mdxFiles: 0 ``` <!-- github-comment-id:979122094 -->

adam commented 2026-10-05 02:29:43 +02:00

Author

Owner

Copy link

Copy source

# Project name

jorgeml

# Folders

- posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/"
- posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts"

# Workspace folder

/var/home/jorgeml/Workspace/blog/jorgeml

# Folders to search files

- Project start length: 8 | Search in: "content/**/*.*" | mdFiles: 0 | mdxFiles: 0
- Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 0 | mdxFiles: 0
    

``` # Project name jorgeml # Folders - posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/" - posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts" # Workspace folder /var/home/jorgeml/Workspace/blog/jorgeml # Folders to search files - Project start length: 8 | Search in: "content/**/*.*" | mdFiles: 0 | mdxFiles: 0 - Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 0 | mdxFiles: 0 ``` <!-- github-comment-id:979126845 -->

adam commented 2026-10-05 02:29:43 +02:00

Author

Owner

Copy link

Copy source

Thanks again, it seems to be related to the VS Code its workspace API of finding files. As a test, I did another update which will just retrieve all files in your current workspace. What I'm expecting is that there is some sort of limitation or restriction that prevents VS Code from using the findFiles method in your workspace.

FIrst let us check what the new BETA Diagnostics output gives.

Thanks again, it seems to be related to the VS Code its workspace API of finding files. As a test, I did another update which will just retrieve all files in your current workspace. What I'm expecting is that there is some sort of limitation or restriction that prevents VS Code from using the `findFiles` method in your workspace. FIrst let us check what the new BETA Diagnostics output gives. <!-- github-comment-id:979146654 -->

adam commented 2026-10-05 02:29:44 +02:00

Author

Owner

Copy link

Copy source

# Project name

jorgeml

# Folders

- posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts"

# Workspace folder

/var/home/jorgeml/Workspace/blog/jorgeml

# Total files

Total files found: 1031

# Folders to search files

- Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 0 | mdxFiles: 0

``` # Project name jorgeml # Folders - posts: "/var/home/jorgeml/Workspace/blog/jorgeml/content/posts" # Workspace folder /var/home/jorgeml/Workspace/blog/jorgeml # Total files Total files found: 1031 # Folders to search files - Project start length: 13 | Search in: "content/posts/**/*.*" | mdFiles: 0 | mdxFiles: 0 ``` <!-- github-comment-id:979195312 -->

adam commented 2026-10-05 02:29:45 +02:00

Author

Owner

Copy link

Copy source

That is good news, but now I'm even more confused 😂

Would you be able to share a screenshot of the project files and folders treeview?

That is good news, but now I'm even more confused 😂 Would you be able to share a screenshot of the project files and folders treeview? <!-- github-comment-id:979217737 -->

adam commented 2026-10-05 02:29:45 +02:00

Author

Owner

Copy link

Copy source

Mystery resolved... Just realised my files have extension ".markdown" instead of ".md". Renaming one of the files made it appear.

I'm truly sorry for wasting your time :-(

Mystery resolved... Just realised my files have extension ".markdown" instead of ".md". Renaming one of the files made it appear. I'm truly sorry for wasting your time :-( <!-- github-comment-id:979235223 -->

adam commented 2026-10-05 02:29:46 +02:00

Author

Owner

Copy link

Copy source

hahaha. 🙃

Ok, so that's pretty easy to get fixed. I'll add support for .markdown files in that case.

hahaha. 🙃 Ok, so that's pretty easy to get fixed. I'll add support for `.markdown` files in that case. <!-- github-comment-id:979245759 -->

adam commented 2026-10-05 02:29:47 +02:00

Author

Owner

Copy link

Copy source

I just renamed all of them. Also standardised on "type: posts" as I had both "post" and "posts" values to the same key.

Thanks for putting together this extension, it's truly awesome.

I just renamed all of them. Also standardised on "type: posts" as I had both "post" and "posts" values to the same key. Thanks for putting together this extension, it's truly awesome. <!-- github-comment-id:979247544 -->

adam commented 2026-10-05 02:29:47 +02:00

Author

Owner

Copy link

Copy source

Support for .markdown has also been added. Just in case others have it as well.

Support for `.markdown` has also been added. Just in case others have it as well. <!-- github-comment-id:979254326 -->

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

beta

dependabot/npm_and_yarn/js-yaml-4.3.1

dependabot/npm_and_yarn/multi-7958ac4c45

dependabot/npm_and_yarn/postcss-8.5.25

dependabot/npm_and_yarn/multi-670d462a53

dependabot/npm_and_yarn/http-proxy-middleware-2.0.10

dependabot/npm_and_yarn/shell-quote-1.10.0

dependabot/npm_and_yarn/websocket-driver-0.7.5

dependabot/npm_and_yarn/multi-6aaed2ab8e

copilot/validate-issue-1043

dependabot/npm_and_yarn/multi-84120a5570

dependabot/npm_and_yarn/launch-editor-2.14.1

dependabot/npm_and_yarn/multi-9dd3b9b346

estruyf/smart-file-rename

copilot/fix-unwanted-auto-update-publish-date

copilot/fix-content-view-sorting-issue

copilot/fix-virtual-workspace-folder-selection

copilot/fix-937

copilot/fix-965

copilot/fix-958

copilot/fix-950

copilot/fix-932

copilot-integration

hotfix/10.2.1

issue/816

issue/671

i18n

azure-translator

issue/747

issue/673

poc/content-tagging

combobox

v10.13.0

v10.12.0

v10.11.0

v10.10.1

v10.10.0

v10.9.0

v10.8.0

v10.7.0

v10.6.0

v10.5.1

v10.5.0

v10.4.1

v10.4.0

v10.3.0

v10.2.1

v10.2.0

v10.1.0

v10.0.2

v10.0.1

v10.0.0

v9.4.0

v9.3.1

v9.3.0

v9.2.0

v9.1.0

v9.0.0

v8.4.0

v8.3.0

v8.2.0

v8.1.2

v8.1.1

v8.1.0

v8.0.1

v8.0.0

v7.3.4

v7.3.3

v7.3.2

v7.3.1

v7.3.0

v7.2.0

v7.1.2

v7.1.1

v7.1.0

v7.0.0

v6.1.1

v6.1.0

v6.0.0

v5.10.0

v5.9.0

v5.8.0

v5.7.0

v5.6.0

v5.5.0

v5.4.0

v5.3.1

v5.3.0

v5.2.0

v5.1.1

v5.1.0

v5.0.0

4.0.1

4.0.0

3.1.0

v3.0.2

v3.0.1

v3.0.0

v2.5.1

v2.5.0

v2.4.1

v2.4.0

v2.3.0

v2.2.0

v2.1.0

v2.0.1

v2.0.0

v1.18.0

v1.17.1

v1.17.0

v1.16.1

v1.16.0

v1.15.1

v1.15.0

Labels

No items

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

adam (Adam Wojcieszonek)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#149