Skip to content

Conversation

@herheliuk
Copy link
Member

Using a wrapper we don't check for sudo on every connection, but
ensure users won't get an Unknown error trying to use the API without sudo.

Signed-off-by: Andrii Herheliuk [email protected]

Using a wrapper we don't check for sudo on every connection, but
ensure users won't get an Unknown error trying to use the API without sudo.

Signed-off-by: Andrii Herheliuk <[email protected]>
@herheliuk herheliuk force-pushed the pycriu-use-binary-error-handling branch from f080e58 to 056bf78 Compare October 23, 2025 18:05
@herheliuk herheliuk changed the title pycriu: better use_binary errors handling pycriu: better use_binary errors handling Oct 23, 2025
@herheliuk
Copy link
Member Author

herheliuk commented Oct 23, 2025

Before:

CHECK failed: Error(0): Unknown

After:

CHECK failed with internal error: Please run with sudo or use service socket instead.

Note that use_sk is not affected by this change at all.

P.S. You are very welcome ^^

@herheliuk herheliuk marked this pull request as ready for review October 23, 2025 18:30
@avagin
Copy link
Member

avagin commented Oct 27, 2025

criu can work without sudo (6a30c7d).

@herheliuk
Copy link
Member Author

herheliuk commented Oct 27, 2025

criu can work without sudo (6a30c7d).

Yes, and this check is only when using pycriu with use_binary

Note that use_sk is not affected by this change at all.

When I tested it I was always getting an error using it via binary without sudo

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.

2 participants