Bugfix/Fix artifact directory not being writable by the hawkbit user#4
Merged
Bugfix/Fix artifact directory not being writable by the hawkbit user#4
Conversation
wborn
approved these changes
Apr 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ran into an issue when uploading artifacts/firmware to hawkBit due to the artifactrepo path not being writable by the
hawkbituser.This is fixed by removing the
VOLUMEfrom the Dockerfile because Docker was treating/opt/hawkbit/artifactrepoas a separate mount point, which obscured the image directory and bypassed the build-time permissions that were set.Built and ran the image locally, and tested whether I could upload an artifact successfully.
