Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Dockerfiles for e2e tests next iteration #1757

Draft
wants to merge 19 commits into
base: trunk
Choose a base branch
from

Conversation

JeremyTubongbanua
Copy link
Member

@JeremyTubongbanua JeremyTubongbanua commented Feb 24, 2025

- What I did

  • Created 4 Dockerfiles, meant to run a container that holds either C binaries or Dart binaries, that are either built from a branch (or commit hash) OR taken from releases.

The 4 Dockerfiles are:

  • Dockerfile.c.branch - build C binaries (sshnpd, srv, at_activate) from a specified branch name or commit hash
  • Dockefile.dart.branch - build Dart binaries from a specified branch name or commit hash
  • Dockerfile.c.release - download C binaries from a specified c.*.*.* release
  • Dockerfile.dart.release - download Dart binaries from the latest release or a specified v.*.*.* release

- How I did it

- How to verify it

  • See README.md on usage of the Dockerfiles

- Description for the changelog
feat: Dockerfiles for e2e tests next iteration

@JeremyTubongbanua
Copy link
Member Author

JeremyTubongbanua commented Feb 24, 2025

This PR is related to #1444

@@ -0,0 +1,31 @@
FROM dart:3.6.0
Copy link
Member

Choose a reason for hiding this comment

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

Should be 3.7.0 and pinned to a hash

Copy link
Member Author

Choose a reason for hiding this comment

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

Where can I find instructions on how to do that again?

Copy link
Member Author

Choose a reason for hiding this comment

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

Never mind , figured it out :)

@JeremyTubongbanua JeremyTubongbanua self-assigned this Feb 25, 2025
@JeremyTubongbanua JeremyTubongbanua marked this pull request as ready for review February 25, 2025 14:47
@JeremyTubongbanua JeremyTubongbanua marked this pull request as draft February 25, 2025 16:01
mkdir -p ${HOMEDIR}/.ssh ${HOMEDIR}/.atsign/keys ; \
chown -R ${USER}:${USER} ${HOMEDIR} ; \
touch ${HOMEDIR}/.ssh/authorized_keys ; \
ex +"%s/^%sudo.*$/%sudo ALL=(ALL:ALL) NOPASSWD:ALL/g" -scwq! /etc/sudoers ; \
Copy link
Member

Choose a reason for hiding this comment

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

why a vim ex command instead of sed?

Copy link
Member

@XavierChanth XavierChanth Mar 3, 2025

Choose a reason for hiding this comment

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

This should be the same as sed -e 's/^%sudo.*$/%sudo ALL=(ALL:ALL) NOPASSWD:ALL/g' -i /etc/sudoers and you don't need to install vim & the vim runtime (which is heavier than just vi)

Copy link
Member Author

Choose a reason for hiding this comment

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

Done in 64fcfee

Copy link
Member

@XavierChanth XavierChanth left a comment

Choose a reason for hiding this comment

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

See my comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants