Skip to content

Conversation

@opajonk
Copy link
Contributor

@opajonk opajonk commented Aug 26, 2025

Here, I have collected a few improvements to the DevContainer which I think should go in before we call this a 1.0.0.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you make use of versions.sh in this file to not repeat the version numbers?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately no, I think. This file belongs to the devcontainer s-core-devcontainer itself, not to the local feature s-core-local (which provides tools for which no existing devcontainer feature can be used). It would be an encapsulation violation to do so.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It does sound wrong to have versions in two places. But I don't understand enough of the setup to propose any solution here.

Also the versions should be easily accessible somehow for unrelated, non-devcontainer usecases. That's probably a topic in itself.

@opajonk opajonk changed the title Collection of Improvements (WIP) Collection of Improvements Sep 5, 2025
@opajonk opajonk requested a review from lurtz September 5, 2025 10:56
duplicate, and it is already in the base-image anyway
otherwise, re-builds of the container may "suddenly" contain unexpected versions of relevant tools
otherwise, re-builds of the container may "suddenly" contain unexpected versions of relevant tools
Since these tools are really important, we should definitely check that the versions are as expected.
Following https://code.visualstudio.com/remote/advancedcontainers/persist-bash-history, this implements an across-container-restarts-persistent bash history.
@opajonk opajonk force-pushed the collection-of-improvements branch from 8b55ce5 to c0ac659 Compare September 5, 2025 11:03
@opajonk
Copy link
Contributor Author

opajonk commented Sep 8, 2025

Getting aarch64 support seems to take too long (external dependency). I will open this now for reviews. When we get aarch64, that can be released as 1.1.x stream.

@opajonk opajonk marked this pull request as ready for review September 8, 2025 12:32
sudo chown "${USERNAME}:${GROUPNAME}" "${COMMANDHISTORY_DIR}"
sudo chmod 755 "${COMMANDHISTORY_DIR}"

# Create .bash_history file if it doesn't exist and set permissions
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me test that one. It has zsh support, which may be not a bad idea.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried it, but it fails to install

0.109 ===========================================================================
0.110 Activating feature 'shell-history'
0.110 User: vscode     User home: 
0.110 ***********************************************************************************
0.110 *** Require _REMOTE_USER and _REMOTE_USER_HOME to be set (by dev container CLI) ***
0.110 ***********************************************************************************
0.110 ERROR: Feature "Shell History" (ghcr.io/stuartleeks/dev-container-features/shell-history) failed to install!

Apparently, there are additional requirements for this feature. For this little advantage, it seems to be too complicated.

AlexanderLanin
AlexanderLanin previously approved these changes Sep 8, 2025
@opajonk opajonk force-pushed the collection-of-improvements branch from d4fe1db to 6e28bbb Compare September 9, 2025 06:07
@AlexanderLanin AlexanderLanin merged commit fae4b2e into eclipse-score:main Sep 9, 2025
2 checks passed
@opajonk opajonk deleted the collection-of-improvements branch September 9, 2025 07:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

3 participants