Codespaces postAttachCommand in devcontainer.json is not running

[johndunderhill]

🏷️ Discussion Type

Bug

Body

The problem is similar to https://github.com/orgs/community/discussions/170692 however in this case the file /workspaces/.codespaces/shared/codespaceStatusTool.js is present. postAttachCommand never runs. We know this because we write a marker file at the start of it. Here's a snippet from devcontainer.json:

	"name": "Costvine Development Container",
	"image": "ghcr.io/costvine/container:main",

	"postStartCommand": "scripts/setup-workspace",
	"postAttachCommand": "scripts/setup-vscode",

And here's scripts/setup-vscode:

#!/bin/bash

# https://github.com/orgs/community/discussions/170692
date >${WORKSPACE_ROOT}/.last-setup-vscode-started

setup-python
ps -aef >/tmp/allprocesses.log
grep "setup-python-daemon" /tmp/allprocesses.log >/dev/null
if [[ $? -ne 0 ]]; then
	setup-python-daemon &
	disown
fi
rm -f /tmp/allprocesses.log
activate-gcloud
show-status

date >${WORKSPACE_ROOT}/.last-setup-vscode-completed

Container was start at Apr 5 07:08 UTC:

@johndunderhill ➜ /workspaces/costvine (dev-john) $ ls -l $WORKSPACE_ROOT/.codespaces/.persistedshare/creation.log
-rw-r--r-- 1 vscode root 7451 Apr  5 07:08 /workspaces/.codespaces/.persistedshare/creation.log

But the script above did not start or finish:

@johndunderhill ➜ /workspaces/costvine (dev-john) $ ls -l ${WORKSPACE_ROOT}/.last-setup-vscode-*
-rw-rw-rw- 1 vscode vscode 32 Apr  4 08:58 /workspaces/.last-setup-vscode-completed
-rw-rw-rw- 1 vscode vscode 32 Apr  4 08:58 /workspaces/.last-setup-vscode-started

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[johndunderhill]

#170692 @cmuto09