Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Configurable user IDs#429

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
etcwilde wants to merge1 commit intoswiftlang:main
base:main
Choose a base branch
Loading
frometcwilde:ewilde/configurable-build-user-id

Conversation

@etcwilde
Copy link
Member

When working with these containers to debug issues locally, it's sometimes useful to have the source directory live on the host, while building in the container. In order for permissions to line up, the user ID numbers need to match or the build-user may not be able to create the necessary directories.

This patch allows setting the build-user user ID so that the permissions line up and the user in the container and host can manipulate the files.

Override the build user ID with the current user's ID is done with the following command to ensure that the permissions on any volumes are kept in sync is the following:
docker build --build-arg BUILD_USER_ID=$(id -u) ...

@etcwilde
Copy link
MemberAuthor

@swift-ci please test

@etcwildeetcwildeforce-pushed theewilde/configurable-build-user-id branch from315ee05 toa6f52e6CompareFebruary 13, 2025 22:04
@etcwilde
Copy link
MemberAuthor

I'm going to need more output than[FAILED] - swift-ci/main/ubuntu/24.04/Dockerfile.
I am unable to reproduce a failure with this Dockerfile locally.

@shahmishal
Copy link
Member

In the artifact step, you should see a link to download the logs.

Artifact download URL:https://github.com/swiftlang/swift-docker/actions/runs/13317949874/artifacts/2589170704

@etcwilde
Copy link
MemberAuthor

CentOS 7:

#6 0.359 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error"

Ubuntu 23.10:

#7 0.293 Ign:1 http://security.ubuntu.com/ubuntu mantic-security InRelease#7 0.293 Ign:2 http://archive.ubuntu.com/ubuntu mantic InRelease#7 0.369 Err:3 http://security.ubuntu.com/ubuntu mantic-security Release#7 0.369   404  Not Found [IP: 185.125.190.83 80]#7 0.369 Ign:4 http://archive.ubuntu.com/ubuntu mantic-updates InRelease#7 0.445 Ign:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease#7 0.521 Err:6 http://archive.ubuntu.com/ubuntu mantic Release#7 0.521   404  Not Found [IP: 185.125.190.83 80]#7 0.598 Err:7 http://archive.ubuntu.com/ubuntu mantic-updates Release#7 0.598   404  Not Found [IP: 185.125.190.83 80]#7 0.674 Err:8 http://archive.ubuntu.com/ubuntu mantic-backports Release#7 0.674   404  Not Found [IP: 185.125.190.83 80]

Ubuntu 24.04:

tar: usr/lib/libLTO.so.15git: Cannot write: No space left on device...

Docc:

#5 ERROR: failed to register layer: write /usr/lib/x86_64-linux-gnu/libicudata.so.57.1: no space left on device

Static SDK

ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref c134ce27-11c9-4288-a10a-13dadbadd510::xc4kljypnmeqd83a464gmh764: "/resources": not found

Most of these look like either the distro is EOL or an infra issue. I can avoid the EOL distros. I'm not sure what is happening with the static SDK though. Will see if I can reproduce that. This change shouldn't have an effect.

@etcwilde
Copy link
MemberAuthor

Ah,ci_test.py is trying to build the static SDK from a different directory than the directory that the Dockerfile is in, which doesn't work because the Dockerfile copies in the resources directory, which is situated next to the Dockerfile.

Running: docker build --no-cache=true -f swift-ci/sdks/static-linux/Dockerfile .

@etcwildeetcwildeforce-pushed theewilde/configurable-build-user-id branch froma6f52e6 to11730a5CompareFebruary 14, 2025 20:37
When working with these containers to debug issues locally, it'ssometimes useful to have the source directory live on the host, whilebuilding in the container. In order for permissions to line up, the userID numbers need to match or the build-user may not be able to createthe necessary directories.This patch allows setting the build-user user ID so that the permissionsline up and the user in the container and host can manipulate the files.Override the build user ID with the current user's ID is done with thefollowing command to ensure that the permissions on any volumes arekept in sync is the following:`docker build --build-arg BUILD_USER_ID=$(id -u) ...`
@etcwildeetcwildeforce-pushed theewilde/configurable-build-user-id branch from11730a5 to6721040CompareFebruary 18, 2025 18:49
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@shahmishalshahmishalshahmishal approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@etcwilde@shahmishal

[8]ページ先頭

©2009-2025 Movatter.jp