[Bug]: container tag `:latest` does not exist

[pawalan]

docmd version

0.8.6

Node.js version

docker

OS/Browser

Linux / Chrome

Description

Documentation mentions in various places to pull the Docker image with

docker pull ghcr.io/docmd-io/docmd:latest

but the image tag latest doesn't seem to exist.

Steps to Reproduce

Run docker pull ghcr.io/docmd-io/docmd:latest or podman pull ghcr.io/docmd-io/docmd:latest.

Expected Behavior

image pulls

[mgks]

Thanks for the report.

You're right, the latest tag was never being applied to the published Docker image as it was intended, I must have missed it in the CI. As an immediate workaround, pull a specific version that does exist:

docker pull ghcr.io/docmd-io/docmd:0.8.6

This issue will be fixed in the next release, and stable releases will be tagged :latest going forward.

[UnclePhil]

Please also align the documentation for:

• The present reported problem (tag)
• The usage of volumes (ex: /workspace) not defined in the dockerfile
• Be sure that the uid 1001 used in dockerfile is mandatory

For me , the only working syntax is :

docker run -v $(pwd):/workspace -w /workspace -u 1000:1000 ghcr.io/docmd-io/docmd:0.8.6 init  

[mgks]

@pawalan confirmed, and fixed for 0.8.7.

The image-publish workflow was missing the latest tag. I forgot to wire it up. It now tags :latest automatically on release events, so docker pull ghcr.io/docmd-io/docmd:latest will work going forward along with the version tag.

Thanks for reporting this and I hope it works for you now.

[UnclePhil]

Tests after release:

Latest tag is working

But

**docker run -v $(pwd):/docs ghcr.io/docmd-io/docmd:latest init **

Still giving permission problems

[docmd] /docs is empty — seeding demo template from /template
cp: can't create '/docs/./docmd.config.json': Permission denied
cp: can't create directory '/docs/./docs': Permission denied
cp: can't create '/docs/./package.json': Permission denied
cp: can't create directory '/docs/./assets': Permission denied
cp: can't create '/docs/./SKILL.md': Permission denied
cp: can't preserve times of '/docs/.': Operation not permitted
cp: can't preserve ownership of '/docs/.': Operation not permitted
cp: can't preserve permissions of '/docs/.': Operation not permitted

and if i use the 1000 user, structure become present in the current folder but still with permission errors

docker run -v $(pwd):/docs -u 1000:1000 ghcr.io/docmd-io/docmd:latest init

[docmd] /docs is empty — seeding demo template from /template
cp: can't preserve ownership of '/docs/./docmd.config.json': Operation not permitted
cp: can't preserve ownership of '/docs/./docs/index.md': Operation not permitted
cp: can't preserve ownership of '/docs/./docs': Operation not permitted
cp: can't preserve ownership of '/docs/./package.json': Operation not permitted
cp: can't preserve ownership of '/docs/./assets/images': Operation not permitted
cp: can't preserve ownership of '/docs/./assets/js': Operation not permitted
cp: can't preserve ownership of '/docs/./assets/css': Operation not permitted
cp: can't preserve ownership of '/docs/./assets': Operation not permitted
cp: can't preserve ownership of '/docs/./SKILL.md': Operation not permitted
cp: can't preserve ownership of '/docs/.': Operation not permitted 

I'm pretty sure that the usage of user 1001 in the image is the reason

[mgks]

@UnclePhil sorry about that, the docs should have covered this from the start, that's on me. Updated the Custom working directory and file ownership section and pushed a fixed image under the same tag.

Pull the updated image and your original commands will work as-is, no flags needed:

docker pull ghcr.io/docmd-io/docmd:latest

# Initialise a new project
docker run -v $(pwd):/docs ghcr.io/docmd-io/docmd:latest init

# Dev server with your own docs
docker run -v $(pwd):/docs -p 3000:3000 ghcr.io/docmd-io/docmd:latest

The entrypoint now starts as root, reads the uid:gid of the mounted directory via stat, and re-execs as that identity before running any command, the same pattern the official postgres and redis images use. Let me know if you hit anything else.

[UnclePhil]

Working correctly at first pass with the (new) latest tag.
all files are created with correct permissions.
So this can be close

But !! (sorry)
At the second pass with the same command
You propose to overwrite all files, and the read is never possible with the command

docker run --rm -v $(pwd):/docs ghcr.io/docmd-io/docmd:latest init

(...)
┌─ Project Setup
│  [ SKIP ] Using existing package.json
⬢ Existing files detected:
│                  docmd.config.json
│                  docs/index.md

 Do you want to override these files? (y/N): 

Because the docker session is not interactive ...
It work when the command become

docker run --rm -it -v $(pwd):/docs ghcr.io/docmd-io/docmd:latest init

(...)

┌─ Project Setup
│  [ SKIP ] Using existing package.json
⬢ Existing files detected:
│                  docmd.config.json
│                  docs/index.md

 Do you want to override these files? (y/N): y
│  [ SKIP ] Using existing docs/ directory
│  [ SKIP ] Using existing assets/ directory
│  [ DONE ] Updated docmd.config.json
│  [ DONE ] Updated docs/index.md
│  [ DONE ] Updated SKILL.md
└──────────────────────────────────────────────────────────

⬢ Initialisation complete. Run `npm install` to setup dependencies.

In conclusion , in you docker documentation add two flags --rm -it to become an interactive session with no container persistence if we are really working on cmdline.

But this is not working if , like me, you are in a CICD chain,
To solve this , you need to add a force flag to the init command (or change the default action)

BTW : I love your project because I need to migrate a lot of mkdocs sites
Nice work !!
Best regards

[mgks]

I'm glad you like working with docmd and thanks for sticking with this. Both issues are confirmed and will be fixed in 0.8.8.

Added fix in 0.8.8:

docker run --rm -v $(pwd):/docs ghcr.io/docmd-io/docmd:latest init --force

Support for --force / -y and proper non-interactive handling has been added.

I'll post an update here once 0.8.8 is released, likely within the next day or two. Thanks again for the detailed testing.

[mgks]

Shipped in 0.8.8. 🚀

• :latest tag now applied on release events only.
• Entrypoint re-execs as host uid:gid via su-exec, so -v $(pwd):/docs works without flags.
• init no longer hangs in non-TTY – --force / -y override explicitly

Thanks for the thorough follow-up testing. @UnclePhil @pawalan

Closing this for now, if the same issue persists, you can open this or create a new issue.