mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 15:15:56 +03:00
[GH-ISSUE #1042] Assets are not populating. #279
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#279
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BloodBlight on GitHub (Oct 21, 2021).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1042
Describe the bug
Both tracked and un-tracked assets are blank after pulling files.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Downloaded assets should be in the list.
Screenshots

Additional context
First time using netboot.xyz.
@antonym commented on GitHub (Oct 22, 2021):
Permissions issue with the external volumes setup? I'd make sure that the users and perms line up so that the app can read the contents off the disk.
@BloodBlight commented on GitHub (Oct 23, 2021):
Everything seems to be set to abc:users:
All of the files were created using the pull asset function and it is able to create new files. Just not see them.
As perms are set, everyone should be able to read...
@BloodBlight commented on GitHub (Nov 16, 2021):
Any ideas on what else I can look for?
@antonym commented on GitHub (Nov 17, 2021):
Only issue I can see are the use of the volumes but mainly because I have not set it up that way before. I would recommend trying to set it up per the instructions on a workstation and see if you can at least get it up and running in the documented way and see if it works at the very least in your environment.
@github-actions[bot] commented on GitHub (Dec 18, 2021):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@antonym commented on GitHub (Jan 23, 2022):
Closing, no activity.